Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70f505481b1d19be01bf85f40971d02e4668c27c230fe174856c5b07401433cc

Tx prefix hash: e80e0947d97e967b94f7d6147fa05505ae647e291bab0e216b937f64523dd3b5
Tx public key: 655539b63d671d99487d8eead5e3e8fc84c2fdd65395ae1e9a55fe11bcb803cc
Timestamp: 1716912441 Timestamp [UCT]: 2024-05-28 16:07:21 Age [y:d:h:m:s]: 01:000:12:55:38
Block: 1031974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261286 RingCT/type: yes/0
Extra: 01655539b63d671d99487d8eead5e3e8fc84c2fdd65395ae1e9a55fe11bcb803cc0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9e96e7c3536ce60a2b1ab987e0ac7858607cd273f0cf011450c58ed91fbaa2f 0.600000000000 1500423 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": 1031984, "vin": [ { "gen": { "height": 1031974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9e96e7c3536ce60a2b1ab987e0ac7858607cd273f0cf011450c58ed91fbaa2f" } } ], "extra": [ 1, 101, 85, 57, 182, 61, 103, 29, 153, 72, 125, 142, 234, 213, 227, 232, 252, 132, 194, 253, 214, 83, 149, 174, 30, 154, 85, 254, 17, 188, 184, 3, 204, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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