Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0789606f7025fb73a8b4d5bb08a7d8de4a7942b171c3f33637ff705b7d03cbfd

Tx prefix hash: 8951d0719677b941d4abf5850a5b41d00015f4dfd6ba4c3892c8b6ba9d959f91
Tx public key: fd9c0983e3c5ad2b5c8c59746fe0f21e9d47261d07bef9aa93bd245646de011e
Timestamp: 1636920383 Timestamp [UCT]: 2021-11-14 20:06:23 Age [y:d:h:m:s]: 03:045:06:14:46
Block: 374334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 811090 RingCT/type: yes/0
Extra: 01fd9c0983e3c5ad2b5c8c59746fe0f21e9d47261d07bef9aa93bd245646de011e02110000000a379224c2000000000000000000

1 output(s) for total of 35.292014786000 dcy

stealth address amount amount idx
00: f8cab7ded6f7975bd61e351de1a56434f5b9e03ed3804677ab1caeb656e22e5d 35.292014786000 757740 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": 374344, "vin": [ { "gen": { "height": 374334 } } ], "vout": [ { "amount": 35292014786, "target": { "key": "f8cab7ded6f7975bd61e351de1a56434f5b9e03ed3804677ab1caeb656e22e5d" } } ], "extra": [ 1, 253, 156, 9, 131, 227, 197, 173, 43, 92, 140, 89, 116, 111, 224, 242, 30, 157, 71, 38, 29, 7, 190, 249, 170, 147, 189, 36, 86, 70, 222, 1, 30, 2, 17, 0, 0, 0, 10, 55, 146, 36, 194, 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