Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 511fdab8c9a0d9ab5c8c5918f7d52b395ce708a6272bfdb73d2dffde85ac47f7

Tx prefix hash: 751ec978f9e92479316dbbe0ba73b33fdbc5f16253cdb826f53381b0dfff31d9
Tx public key: 549d24c9193e063ca1cb0f65345d80009302bcf4916cfd6fb543f54f87130e35
Timestamp: 1717509783 Timestamp [UCT]: 2024-06-04 14:03:03 Age [y:d:h:m:s]: 00:270:04:35:53
Block: 1036920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193061 RingCT/type: yes/0
Extra: 01549d24c9193e063ca1cb0f65345d80009302bcf4916cfd6fb543f54f87130e3502110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0ec5ae5ddb40bf0a47d79f7be171e031afdac47f6c3b7734a9b963b57b8cd37 0.600000000000 1505451 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1036930, "vin": [ { "gen": { "height": 1036920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0ec5ae5ddb40bf0a47d79f7be171e031afdac47f6c3b7734a9b963b57b8cd37" } } ], "extra": [ 1, 84, 157, 36, 201, 25, 62, 6, 60, 161, 203, 15, 101, 52, 93, 128, 0, 147, 2, 188, 244, 145, 108, 253, 111, 181, 67, 245, 79, 135, 19, 14, 53, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8