Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ada506db61897fe177f62c247e876a6e1c2c2240e7c7917a4d483a878e31153

Tx prefix hash: f2481bc7300e08012b1d3db68a4a3945ef4d69e8e743a614109a5b6ecff62371
Tx public key: 85303fdb2371cde28d4b91ad2512f1d21b7d32ea31711666a1c47ca2656a92d2
Timestamp: 1707649168 Timestamp [UCT]: 2024-02-11 10:59:28 Age [y:d:h:m:s]: 01:015:20:01:24
Block: 955152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272327 RingCT/type: yes/0
Extra: 0185303fdb2371cde28d4b91ad2512f1d21b7d32ea31711666a1c47ca2656a92d202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bad5bb57459c9b6dab76e26873f513188253712b9c04eba192154264397cb1a8 0.600000000000 1414438 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": 955162, "vin": [ { "gen": { "height": 955152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bad5bb57459c9b6dab76e26873f513188253712b9c04eba192154264397cb1a8" } } ], "extra": [ 1, 133, 48, 63, 219, 35, 113, 205, 226, 141, 75, 145, 173, 37, 18, 241, 210, 27, 125, 50, 234, 49, 113, 22, 102, 161, 196, 124, 162, 101, 106, 146, 210, 2, 17, 0, 0, 0, 1, 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