Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 540b139540a3f80f9fd8a5090e22ab00de9879d55fafd2c33b74a19d7e430efc

Tx prefix hash: 82fb93f79e7683dfa02ec884b2893e89d111acccc1fab8b49910bcd5a50d0621
Tx public key: 464784e1192b9113cd2fe614d7a123c92e2c2df568aa6852ec689d8b7378cf60
Timestamp: 1712059940 Timestamp [UCT]: 2024-04-02 12:12:20 Age [y:d:h:m:s]: 00:326:04:07:46
Block: 991702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233189 RingCT/type: yes/0
Extra: 01464784e1192b9113cd2fe614d7a123c92e2c2df568aa6852ec689d8b7378cf6002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10ee37974e9cda472cfbc3bffccc5bc73364dfad2e091aba761b9a7b3e3663e4 0.600000000000 1452038 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": 991712, "vin": [ { "gen": { "height": 991702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10ee37974e9cda472cfbc3bffccc5bc73364dfad2e091aba761b9a7b3e3663e4" } } ], "extra": [ 1, 70, 71, 132, 225, 25, 43, 145, 19, 205, 47, 230, 20, 215, 161, 35, 201, 46, 44, 45, 245, 104, 170, 104, 82, 236, 104, 157, 139, 115, 120, 207, 96, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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