Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a54e2a1aedf8b2912040e9eb1b55721965fe18e25197c660c0932957abf6d51

Tx prefix hash: 70246eef6665507d4cf4d42f689e79b8dbe98778c9d6ac2d90f97b1199f51ac4
Tx public key: a6852cd45971b6e5eb4a53356346f9c320603a2e343e960bd4f85c2a1919c0bd
Timestamp: 1755304276 Timestamp [UCT]: 2025-08-16 00:31:16 Age [y:d:h:m:s]: 00:090:05:39:57
Block: 1347530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64226 RingCT/type: yes/0
Extra: 01a6852cd45971b6e5eb4a53356346f9c320603a2e343e960bd4f85c2a1919c0bd02110000000525a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0942748d1a24cab153340fc5b2fba1e55b66f95aef77ebfdd545863b99777726 0.600000000000 1835447 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": 1347540, "vin": [ { "gen": { "height": 1347530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0942748d1a24cab153340fc5b2fba1e55b66f95aef77ebfdd545863b99777726" } } ], "extra": [ 1, 166, 133, 44, 212, 89, 113, 182, 229, 235, 74, 83, 53, 99, 70, 249, 195, 32, 96, 58, 46, 52, 62, 150, 11, 212, 248, 92, 42, 25, 25, 192, 189, 2, 17, 0, 0, 0, 5, 37, 163, 90, 15, 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