Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e2aa6453be196830a838f466e4e2a0dec4a86424a362e4751eeb062e206386b

Tx prefix hash: fb270f33eca8a7b70f56fa0de72ea07673e8855dd1dc18389abd0ea19fac58b7
Tx public key: 8ba1f7e9ff2db41ede573d26ab737d5a9733663f43d56384d292859a3c81d59d
Timestamp: 1699787613 Timestamp [UCT]: 2023-11-12 11:13:33 Age [y:d:h:m:s]: 01:185:13:49:31
Block: 889987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393834 RingCT/type: yes/0
Extra: 018ba1f7e9ff2db41ede573d26ab737d5a9733663f43d56384d292859a3c81d59d021100000001679a8a81000000000000000000

1 output(s) for total of 0.690404504000 dcy

stealth address amount amount idx
00: 600be4a6c719f6b54e4816ca6e3c9d7f6ecf475085d7913056ac1e6180db6b17 0.690404504000 1346006 of 0

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": 889997, "vin": [ { "gen": { "height": 889987 } } ], "vout": [ { "amount": 690404504, "target": { "key": "600be4a6c719f6b54e4816ca6e3c9d7f6ecf475085d7913056ac1e6180db6b17" } } ], "extra": [ 1, 139, 161, 247, 233, 255, 45, 180, 30, 222, 87, 61, 38, 171, 115, 125, 90, 151, 51, 102, 63, 67, 213, 99, 132, 210, 146, 133, 154, 60, 129, 213, 157, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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