Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2036cc92bbbc9455c5ce39d90a9c207a271d0e4e70acbb348b2b122c51f1af6

Tx prefix hash: f84813fd479ca8562e1c850ac711657d32798695114710b1bbdc9b961046c003
Tx public key: ca3ea68b4cb4cbb72d5852f490018f4bf025399d701c03d6aa17c4d519a7c3ce
Timestamp: 1752657896 Timestamp [UCT]: 2025-07-16 09:24:56 Age [y:d:h:m:s]: 00:195:13:07:33
Block: 1326631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138415 RingCT/type: yes/0
Extra: 01ca3ea68b4cb4cbb72d5852f490018f4bf025399d701c03d6aa17c4d519a7c3ce021100000013bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 736bc3dd8db139d8932c1dbf60ede464319238faa4d5f1b0f11dca879bc779b1 0.600000000000 1814382 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": 1326641, "vin": [ { "gen": { "height": 1326631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "736bc3dd8db139d8932c1dbf60ede464319238faa4d5f1b0f11dca879bc779b1" } } ], "extra": [ 1, 202, 62, 166, 139, 76, 180, 203, 183, 45, 88, 82, 244, 144, 1, 143, 75, 240, 37, 57, 157, 112, 28, 3, 214, 170, 23, 196, 213, 25, 167, 195, 206, 2, 17, 0, 0, 0, 19, 191, 81, 178, 162, 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