Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a15639b1ee69d4ead2bfee41551e10d80676f2372f277295e08642b1ccd1bc2c

Tx prefix hash: 029f0dc42f472a8e43694ddb57421ff2376e9030f8e73e6f488d98988491c730
Tx public key: fd25098c20d68a40b5c54aada68f1bbb923001f75df5bd6f4be560feb70f72bb
Timestamp: 1732786079 Timestamp [UCT]: 2024-11-28 09:27:59 Age [y:d:h:m:s]: 00:167:20:51:48
Block: 1163467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119809 RingCT/type: yes/0
Extra: 01fd25098c20d68a40b5c54aada68f1bbb923001f75df5bd6f4be560feb70f72bb0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfe584c8a0d8371099a9ac3df5d70b6edb46fedc8d24314cb467753703543a89 0.600000000000 1649134 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": 1163477, "vin": [ { "gen": { "height": 1163467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfe584c8a0d8371099a9ac3df5d70b6edb46fedc8d24314cb467753703543a89" } } ], "extra": [ 1, 253, 37, 9, 140, 32, 214, 138, 64, 181, 197, 74, 173, 166, 143, 27, 187, 146, 48, 1, 247, 93, 245, 189, 111, 75, 229, 96, 254, 183, 15, 114, 187, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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