Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30fd3fe258c0a7db4c9303bc6e796be59f45870c78b14a4fa2a49f660969ffb2

Tx prefix hash: 9cff96a5b2062fa05276c826f0055f5371f6334eafee1086f64fadf57db1bd35
Tx public key: 0af7da4ac6f41c4bb8dd4974be133549d5f735a5ec7b483744f9e6c2ebac9c15
Timestamp: 1728803872 Timestamp [UCT]: 2024-10-13 07:17:52 Age [y:d:h:m:s]: 00:239:22:59:03
Block: 1130551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171325 RingCT/type: yes/0
Extra: 010af7da4ac6f41c4bb8dd4974be133549d5f735a5ec7b483744f9e6c2ebac9c1502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3e66bc29183c42ee08c8127bc066d2cf36c7f75492e2514702b60d6514d33c2 0.600000000000 1613428 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": 1130561, "vin": [ { "gen": { "height": 1130551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3e66bc29183c42ee08c8127bc066d2cf36c7f75492e2514702b60d6514d33c2" } } ], "extra": [ 1, 10, 247, 218, 74, 198, 244, 28, 75, 184, 221, 73, 116, 190, 19, 53, 73, 213, 247, 53, 165, 236, 123, 72, 55, 68, 249, 230, 194, 235, 172, 156, 21, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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