Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35c5da513d35267f1e6aa72c9f643712cf5735cabb89f1107fde44ac707d346b

Tx prefix hash: 1b9fd35e6d58446c3dddda32b001ad64618fcff02682f7fdb85a2a35bf63cc06
Tx public key: dfc85eb3e359aa418cdf290b250f4a0c6e8b8efb412a99857eee21283f078dc9
Timestamp: 1755994105 Timestamp [UCT]: 2025-08-24 00:08:25 Age [y:d:h:m:s]: 00:161:11:52:59
Block: 1353041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115268 RingCT/type: yes/0
Extra: 01dfc85eb3e359aa418cdf290b250f4a0c6e8b8efb412a99857eee21283f078dc90211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4ece32eb4a552aedbb69e35b979119b096f38f9626370075c16c70c835fd77d 0.600000000000 1841012 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": 1353051, "vin": [ { "gen": { "height": 1353041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4ece32eb4a552aedbb69e35b979119b096f38f9626370075c16c70c835fd77d" } } ], "extra": [ 1, 223, 200, 94, 179, 227, 89, 170, 65, 140, 223, 41, 11, 37, 15, 74, 12, 110, 139, 142, 251, 65, 42, 153, 133, 126, 238, 33, 40, 63, 7, 141, 201, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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