Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f082eae06ebfc94ec3886e90a52fa030e50ea5929b113ef9a59551e5253f1a8

Tx prefix hash: 3fa883d8ff2dc7882c8a3a5d85dd011011ade46840c871c2b7e7a3573878d8ca
Tx public key: d3a89d58eabdc997f006340001d1d5ca6a0089f8405ad4d8851098e1f64537b0
Timestamp: 1732144049 Timestamp [UCT]: 2024-11-20 23:07:29 Age [y:d:h:m:s]: 00:127:00:37:04
Block: 1158131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90595 RingCT/type: yes/0
Extra: 01d3a89d58eabdc997f006340001d1d5ca6a0089f8405ad4d8851098e1f64537b00211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10105b4e85a4ceb2722d8cefe9452d961edcb731608df87004ad1bfa7ca5c054 0.600000000000 1643760 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": 1158141, "vin": [ { "gen": { "height": 1158131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10105b4e85a4ceb2722d8cefe9452d961edcb731608df87004ad1bfa7ca5c054" } } ], "extra": [ 1, 211, 168, 157, 88, 234, 189, 201, 151, 240, 6, 52, 0, 1, 209, 213, 202, 106, 0, 137, 248, 64, 90, 212, 216, 133, 16, 152, 225, 246, 69, 55, 176, 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