Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 896b640c2323f41e9b884a2b9d009d0171067b1eb64e59debe5a257b3ee653de

Tx prefix hash: 587907c83e7365113be7352bf3d53877e42cfe39e5d47af9e5484f774e76b9b2
Tx public key: 1d9780cb8c35323f2ae7e475a5f4811024cfa83b48ca51d7af5cd075c12b9cad
Timestamp: 1735713162 Timestamp [UCT]: 2025-01-01 06:32:42 Age [y:d:h:m:s]: 00:092:02:19:04
Block: 1187688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65608 RingCT/type: yes/0
Extra: 011d9780cb8c35323f2ae7e475a5f4811024cfa83b48ca51d7af5cd075c12b9cad021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53bea8decc37dc0e64cea81db3a4136d93c64f9928e804d3993d911ffff47f11 0.600000000000 1674181 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": 1187698, "vin": [ { "gen": { "height": 1187688 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53bea8decc37dc0e64cea81db3a4136d93c64f9928e804d3993d911ffff47f11" } } ], "extra": [ 1, 29, 151, 128, 203, 140, 53, 50, 63, 42, 231, 228, 117, 165, 244, 129, 16, 36, 207, 168, 59, 72, 202, 81, 215, 175, 92, 208, 117, 193, 43, 156, 173, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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