Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef0f10904270d4814c3e1201f0c22a262a51bfa6a6350f3581016a8cfb489b67

Tx prefix hash: 45e659f7938c81ce72ec8b274bc726d3ed8627919816585c9a8d968d4d50833c
Tx public key: e9ee5053725f38e016f28e0757b7a1f7472b1dd3ff147d5b37f849aaef3087d1
Timestamp: 1707838598 Timestamp [UCT]: 2024-02-13 15:36:38 Age [y:d:h:m:s]: 01:271:05:57:44
Block: 956727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452624 RingCT/type: yes/0
Extra: 01e9ee5053725f38e016f28e0757b7a1f7472b1dd3ff147d5b37f849aaef3087d10211000000117a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc4404ef9c56002a8589d000efd237fc3d68008b0e6526502de3933f0fa418a6 0.600000000000 1416037 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": 956737, "vin": [ { "gen": { "height": 956727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc4404ef9c56002a8589d000efd237fc3d68008b0e6526502de3933f0fa418a6" } } ], "extra": [ 1, 233, 238, 80, 83, 114, 95, 56, 224, 22, 242, 142, 7, 87, 183, 161, 247, 71, 43, 29, 211, 255, 20, 125, 91, 55, 248, 73, 170, 239, 48, 135, 209, 2, 17, 0, 0, 0, 17, 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