Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb0551a0402c94ac664a2e234ece1ed828429189ee79f55dc545ed1b405df73e

Tx prefix hash: b4c67122fd5221fc75ede4fc404a6dd6b4ff4addd8322db1e9e43fd6071d305c
Tx public key: d088976c4552f0b47251763e81118dc9aa78e13eac8b763063f1261acd774040
Timestamp: 1706449428 Timestamp [UCT]: 2024-01-28 13:43:48 Age [y:d:h:m:s]: 01:288:20:07:48
Block: 945186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 465246 RingCT/type: yes/0
Extra: 01d088976c4552f0b47251763e81118dc9aa78e13eac8b763063f1261acd77404002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdcd216c89a9e7c7661819f31d7a7743b1c61880e3eca6c895e3c36150e2f903 0.600000000000 1403496 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": 945196, "vin": [ { "gen": { "height": 945186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdcd216c89a9e7c7661819f31d7a7743b1c61880e3eca6c895e3c36150e2f903" } } ], "extra": [ 1, 208, 136, 151, 108, 69, 82, 240, 180, 114, 81, 118, 62, 129, 17, 141, 201, 170, 120, 225, 62, 172, 139, 118, 48, 99, 241, 38, 26, 205, 119, 64, 64, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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