Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e0da345806f075ae6687452e2d8130064ce67a984b36b4dbd3896df759d4288

Tx prefix hash: dd8ae8b3326355e9d84befbc391dd39c0d24a8c597b29a5645d0496fa68f9339
Tx public key: 2cbbc79b888b334800f26f5de5b2fbae7d213399374bc646f0e871fcf474f33c
Timestamp: 1752608695 Timestamp [UCT]: 2025-07-15 19:44:55 Age [y:d:h:m:s]: 00:198:06:49:37
Block: 1326229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140382 RingCT/type: yes/0
Extra: 012cbbc79b888b334800f26f5de5b2fbae7d213399374bc646f0e871fcf474f33c021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62d549cb41b65b7d8eb7d44f7e3075d6b2efcc6b52018c9c9c4f50470552435e 0.600000000000 1813980 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": 1326239, "vin": [ { "gen": { "height": 1326229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62d549cb41b65b7d8eb7d44f7e3075d6b2efcc6b52018c9c9c4f50470552435e" } } ], "extra": [ 1, 44, 187, 199, 155, 136, 139, 51, 72, 0, 242, 111, 93, 229, 178, 251, 174, 125, 33, 51, 153, 55, 75, 198, 70, 240, 232, 113, 252, 244, 116, 243, 60, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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