Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a819efe66afd6911fc075c8a5fe8e72790fc31d546887367eecde77dbc2e38c

Tx prefix hash: e15db410e5bedf8cd59d106df2603c5bf82edd68d203fe0146e357ef90d087cb
Tx public key: 69177f599b8ee58e6a18026dee8a3fadf729fc511c1bdebb1b165a0f3bec25a3
Timestamp: 1737847242 Timestamp [UCT]: 2025-01-25 23:20:42 Age [y:d:h:m:s]: 00:299:02:18:55
Block: 1205317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211301 RingCT/type: yes/0
Extra: 0169177f599b8ee58e6a18026dee8a3fadf729fc511c1bdebb1b165a0f3bec25a302110000000e007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce2f8ea7dc8eac1556dce8fbcf6cd297b628c0f4a973d47ad52638c64a6067b4 0.600000000000 1692014 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": 1205327, "vin": [ { "gen": { "height": 1205317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce2f8ea7dc8eac1556dce8fbcf6cd297b628c0f4a973d47ad52638c64a6067b4" } } ], "extra": [ 1, 105, 23, 127, 89, 155, 142, 229, 142, 106, 24, 2, 109, 238, 138, 63, 173, 247, 41, 252, 81, 28, 27, 222, 187, 27, 22, 90, 15, 59, 236, 37, 163, 2, 17, 0, 0, 0, 14, 0, 127, 151, 138, 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