Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2b31aa68c1adce077949c7fcfe60b0a5a04cfda01c122a6dc893ce6f84ef0b3

Tx prefix hash: e8d2e05ca6fd80f4bd57b61d14bde40713fd7e2113ec61a4da3385fdad177298
Tx public key: 0b13795dccb43f63a524a7edcbc49fcd09af93f64ae0bb683af9568d47e8b934
Timestamp: 1656968567 Timestamp [UCT]: 2022-07-04 21:02:47 Age [y:d:h:m:s]: 02:182:19:56:48
Block: 536689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 652033 RingCT/type: yes/0
Extra: 010b13795dccb43f63a524a7edcbc49fcd09af93f64ae0bb683af9568d47e8b93402110000000333af99f4000000000000000000

1 output(s) for total of 10.226492509000 dcy

stealth address amount amount idx
00: 3d2089a1c865b583c98c706c92f0b2a119c9a4cb2e1e9fa928c87d0e8cb88abd 10.226492509000 966478 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": 536699, "vin": [ { "gen": { "height": 536689 } } ], "vout": [ { "amount": 10226492509, "target": { "key": "3d2089a1c865b583c98c706c92f0b2a119c9a4cb2e1e9fa928c87d0e8cb88abd" } } ], "extra": [ 1, 11, 19, 121, 93, 204, 180, 63, 99, 165, 36, 167, 237, 203, 196, 159, 205, 9, 175, 147, 246, 74, 224, 187, 104, 58, 249, 86, 141, 71, 232, 185, 52, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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