Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82580745eeefd25e93698db5c93e8cf7771f1e0fbd001ca1fcfe69935a37a89a

Tx prefix hash: 337c1c72ec6488a409baaf32678078443d68fd2ddee0e9448a8a445a9ceed99f
Tx public key: c8312d98d24eec2e21064f09efde0f46791ced122b375354aa6d68145b24d2ae
Timestamp: 1705126764 Timestamp [UCT]: 2024-01-13 06:19:24 Age [y:d:h:m:s]: 01:326:04:53:22
Block: 934224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492010 RingCT/type: yes/0
Extra: 01c8312d98d24eec2e21064f09efde0f46791ced122b375354aa6d68145b24d2ae02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af9929ab9582ebf6c525b6f6080a0aa717e5e853a3fb0ed4dd595f44d3b3e4d8 0.600000000000 1392214 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": 934234, "vin": [ { "gen": { "height": 934224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af9929ab9582ebf6c525b6f6080a0aa717e5e853a3fb0ed4dd595f44d3b3e4d8" } } ], "extra": [ 1, 200, 49, 45, 152, 210, 78, 236, 46, 33, 6, 79, 9, 239, 222, 15, 70, 121, 28, 237, 18, 43, 55, 83, 84, 170, 109, 104, 20, 91, 36, 210, 174, 2, 17, 0, 0, 0, 7, 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