Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5dc75d77ff4c850394a646e4c20018c37c806881e7f70929cdab77a8e66d7e26

Tx prefix hash: f040297c3f3393618793de702636794114f1af7f3c4dd50cee3f2ad9b0f4f8aa
Tx public key: 6f5f77198884470994932c6b8c15df4a92509ed27e4c9f88a7bd29d1035f9562
Timestamp: 1729320049 Timestamp [UCT]: 2024-10-19 06:40:49 Age [y:d:h:m:s]: 00:169:18:20:29
Block: 1134817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121103 RingCT/type: yes/0
Extra: 016f5f77198884470994932c6b8c15df4a92509ed27e4c9f88a7bd29d1035f95620211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1205c102e7b27e8e4e285d8b6c0ac06ee60d22a3240bc225a4bc3dd8d24747b6 0.600000000000 1618144 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": 1134827, "vin": [ { "gen": { "height": 1134817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1205c102e7b27e8e4e285d8b6c0ac06ee60d22a3240bc225a4bc3dd8d24747b6" } } ], "extra": [ 1, 111, 95, 119, 25, 136, 132, 71, 9, 148, 147, 44, 107, 140, 21, 223, 74, 146, 80, 158, 210, 126, 76, 159, 136, 167, 189, 41, 209, 3, 95, 149, 98, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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