Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f8140df4264f28dd118dc2e9ab8f181a1e344b3ab179e88d996f6ba0222b546

Tx prefix hash: ed103d9d44694b1d89f343f8306d2419ef1b077806d8fbca25f8d49033dbc6bd
Tx public key: 7e1378a4309c225e3eb9fb92fcddd7eefee8748143fae00b63e193b6993dcaf7
Timestamp: 1707895843 Timestamp [UCT]: 2024-02-14 07:30:43 Age [y:d:h:m:s]: 01:049:18:10:03
Block: 957196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296598 RingCT/type: yes/0
Extra: 017e1378a4309c225e3eb9fb92fcddd7eefee8748143fae00b63e193b6993dcaf702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81db38939d679127b362b17f22f00e99a82f8d63b1aa200e6fd4f244807a6bc8 0.600000000000 1416512 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": 957206, "vin": [ { "gen": { "height": 957196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81db38939d679127b362b17f22f00e99a82f8d63b1aa200e6fd4f244807a6bc8" } } ], "extra": [ 1, 126, 19, 120, 164, 48, 156, 34, 94, 62, 185, 251, 146, 252, 221, 215, 238, 254, 232, 116, 129, 67, 250, 224, 11, 99, 225, 147, 182, 153, 61, 202, 247, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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