Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 797074ac50f9b76d50402b869f8424e6c8bb440b16447c0c6bf9ea641ba52173

Tx prefix hash: b575ea6b70eec8d3ce94e641a7ecbfe754c8917ab149258fd04861a9908f0c3a
Tx public key: 5fd69b8c5c4d6c9fc34c7a78e3de5ee3b54189f1147531053490d5a29b8b8cf1
Timestamp: 1648658496 Timestamp [UCT]: 2022-03-30 16:41:36 Age [y:d:h:m:s]: 02:269:12:39:16
Block: 469688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 712257 RingCT/type: yes/0
Extra: 015fd69b8c5c4d6c9fc34c7a78e3de5ee3b54189f1147531053490d5a29b8b8cf102110000000fcb8520c2000000000000000000

1 output(s) for total of 17.050178466000 dcy

stealth address amount amount idx
00: bc6262dfd6808d43aa919f6874b9f7ba20dff1969419d4e3e56d843b464116e3 17.050178466000 888684 of 0

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": 469698, "vin": [ { "gen": { "height": 469688 } } ], "vout": [ { "amount": 17050178466, "target": { "key": "bc6262dfd6808d43aa919f6874b9f7ba20dff1969419d4e3e56d843b464116e3" } } ], "extra": [ 1, 95, 214, 155, 140, 92, 77, 108, 159, 195, 76, 122, 120, 227, 222, 94, 227, 181, 65, 137, 241, 20, 117, 49, 5, 52, 144, 213, 162, 155, 139, 140, 241, 2, 17, 0, 0, 0, 15, 203, 133, 32, 194, 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