Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c52fc26bfffe2fc1d016c53b513ffdd549e3d4d0b3f6eb85c340a775151efff

Tx prefix hash: afd3d572b9bbf134103376168c3c4af2732ae3268ae3fabd256b35133d12d12e
Tx public key: e74500074554a39136d0a2309e5fe8a1b8b5c200cd8bdd0adfc5b80b98fee9c7
Timestamp: 1681515727 Timestamp [UCT]: 2023-04-14 23:42:07 Age [y:d:h:m:s]: 01:356:16:21:13
Block: 738737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516207 RingCT/type: yes/0
Extra: 01e74500074554a39136d0a2309e5fe8a1b8b5c200cd8bdd0adfc5b80b98fee9c7021100000003b3164c24000000000000000000

1 output(s) for total of 2.189061054000 dcy

stealth address amount amount idx
00: 3bea1bf000b0898a3c5140da237b2c4da7327f53fd3fed29c5ee694891b953df 2.189061054000 1185482 of 0

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": 738747, "vin": [ { "gen": { "height": 738737 } } ], "vout": [ { "amount": 2189061054, "target": { "key": "3bea1bf000b0898a3c5140da237b2c4da7327f53fd3fed29c5ee694891b953df" } } ], "extra": [ 1, 231, 69, 0, 7, 69, 84, 163, 145, 54, 208, 162, 48, 158, 95, 232, 161, 184, 181, 194, 0, 205, 139, 221, 10, 223, 197, 184, 11, 152, 254, 233, 199, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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