Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7e43d0121253a7309ee228c03e4a14c1770ac2277d2539fd5bdcf6dbe3f4b17

Tx prefix hash: d3ccdfaf0054d10eee2b697b1e4b86c70472228fdff20924d37c224b94182fdd
Tx public key: 7a26bcee8bcd46447fe4aa302f67b1f60068572a54e96b459f6bf8c83ec7c114
Timestamp: 1757836571 Timestamp [UCT]: 2025-09-14 07:56:11 Age [y:d:h:m:s]: 00:067:16:29:09
Block: 1368130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48452 RingCT/type: yes/0
Extra: 017a26bcee8bcd46447fe4aa302f67b1f60068572a54e96b459f6bf8c83ec7c114021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a513bb3e2f9951642a598ff7c5fd5f210f204e7527090406b827f2afa218174e 0.600000000000 1856173 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": 1368140, "vin": [ { "gen": { "height": 1368130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a513bb3e2f9951642a598ff7c5fd5f210f204e7527090406b827f2afa218174e" } } ], "extra": [ 1, 122, 38, 188, 238, 139, 205, 70, 68, 127, 228, 170, 48, 47, 103, 177, 246, 0, 104, 87, 42, 84, 233, 107, 69, 159, 107, 248, 200, 62, 199, 193, 20, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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