Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bb53a9334e998ea1f6ada6088aad44f84d35f8102f22e0ebfc92e8283491f18

Tx prefix hash: 37df427df857d649d67d3324e6ed616ba1ed5d119adb2c02bf96494f7407580f
Tx public key: fd24f1bcb174c93c588e281cdb49af866a43ccc77fddfdf727fc1cb859aa4376
Timestamp: 1710830737 Timestamp [UCT]: 2024-03-19 06:45:37 Age [y:d:h:m:s]: 01:017:02:09:42
Block: 981562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273177 RingCT/type: yes/0
Extra: 01fd24f1bcb174c93c588e281cdb49af866a43ccc77fddfdf727fc1cb859aa437602110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fe533494e1ddec2e2aa1b9ea872cf90f5d01fdaacaebfc4e65d1b9199dd7d4c 0.600000000000 1441659 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": 981572, "vin": [ { "gen": { "height": 981562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fe533494e1ddec2e2aa1b9ea872cf90f5d01fdaacaebfc4e65d1b9199dd7d4c" } } ], "extra": [ 1, 253, 36, 241, 188, 177, 116, 201, 60, 88, 142, 40, 28, 219, 73, 175, 134, 106, 67, 204, 199, 127, 221, 253, 247, 39, 252, 28, 184, 89, 170, 67, 118, 2, 17, 0, 0, 0, 9, 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