Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b9f5d696ba728c7ac162d3c510e7affcf95dbc0c4445759e7cac10ebe0b00a9

Tx prefix hash: e7738c436bb064f01449cd3275d44e398f3b850d614ae2dce045fa86aca9c8c3
Tx public key: 7b0fb2bd3f4f3e162336e60f9280025cf4b44cf726790221a93f78ba96a478b1
Timestamp: 1694899344 Timestamp [UCT]: 2023-09-16 21:22:24 Age [y:d:h:m:s]: 01:202:19:20:26
Block: 849647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406024 RingCT/type: yes/0
Extra: 017b0fb2bd3f4f3e162336e60f9280025cf4b44cf726790221a93f78ba96a478b10211000000014b8f5122000000000000000000

1 output(s) for total of 0.939218938000 dcy

stealth address amount amount idx
00: b36768fc5410798cb845691be76082682908cff2c2d62664f381b978e5204fa8 0.939218938000 1303321 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": 849657, "vin": [ { "gen": { "height": 849647 } } ], "vout": [ { "amount": 939218938, "target": { "key": "b36768fc5410798cb845691be76082682908cff2c2d62664f381b978e5204fa8" } } ], "extra": [ 1, 123, 15, 178, 189, 63, 79, 62, 22, 35, 54, 230, 15, 146, 128, 2, 92, 244, 180, 76, 247, 38, 121, 2, 33, 169, 63, 120, 186, 150, 164, 120, 177, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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