Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dace122fa3a069ca57bf03a0dbcc0fc01f0b3588b00b8d550e637754df3e6ffc

Tx prefix hash: fc4cfa961c5641f1bcdff04e1af6029d34e14692f96c7b6e47516b45b8b3f256
Tx public key: 0cdb36cf3bcd48f7958559e7ef3fc3dfbe555d2402935ff9ae57018e4ea9e178
Timestamp: 1721750469 Timestamp [UCT]: 2024-07-23 16:01:09 Age [y:d:h:m:s]: 00:257:07:02:28
Block: 1072055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183799 RingCT/type: yes/0
Extra: 010cdb36cf3bcd48f7958559e7ef3fc3dfbe555d2402935ff9ae57018e4ea9e17802110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e9ed3eaf724fd7e92120689518118c206f8126a8642b6048e0ddc9a2e92b5d4 0.600000000000 1544490 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": 1072065, "vin": [ { "gen": { "height": 1072055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e9ed3eaf724fd7e92120689518118c206f8126a8642b6048e0ddc9a2e92b5d4" } } ], "extra": [ 1, 12, 219, 54, 207, 59, 205, 72, 247, 149, 133, 89, 231, 239, 63, 195, 223, 190, 85, 93, 36, 2, 147, 95, 249, 174, 87, 1, 142, 78, 169, 225, 120, 2, 17, 0, 0, 0, 12, 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