Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4795f8a1c7d63228543ccdb60457b7d583f9f902d5af64af686a72d2823f9605

Tx prefix hash: 5daa726a1d091b7421ddd675bea71c4e50abca5b9386ff566a3e7e7de76fab84
Tx public key: 6cff8d0ca5dbb1aa6ab4c17914d29df9f8d75a65332afbe102a7ecede280232b
Timestamp: 1728129563 Timestamp [UCT]: 2024-10-05 11:59:23 Age [y:d:h:m:s]: 00:049:16:34:49
Block: 1124957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35492 RingCT/type: yes/0
Extra: 016cff8d0ca5dbb1aa6ab4c17914d29df9f8d75a65332afbe102a7ecede280232b02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc86b0865ca170d3db551d65a8aaacf6d109f3a398563d14b7a0222bb2978904 0.600000000000 1607630 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": 1124967, "vin": [ { "gen": { "height": 1124957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc86b0865ca170d3db551d65a8aaacf6d109f3a398563d14b7a0222bb2978904" } } ], "extra": [ 1, 108, 255, 141, 12, 165, 219, 177, 170, 106, 180, 193, 121, 20, 210, 157, 249, 248, 215, 90, 101, 51, 42, 251, 225, 2, 167, 236, 237, 226, 128, 35, 43, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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