Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e06cbc8adfd08e6aa1eb1ad504be9985ae8026cd897f6d35859f80ff5b1c3a9

Tx prefix hash: 681cb71ec7562ab371506231d9ace64e7ccbac577bc1a8948b363231b3d6fcb3
Tx public key: d31c63c1dd1743c845e6497a4b45dc223a290565e669060d8086df1aeff28674
Timestamp: 1723651007 Timestamp [UCT]: 2024-08-14 15:56:47 Age [y:d:h:m:s]: 00:271:14:03:54
Block: 1087827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194000 RingCT/type: yes/0
Extra: 01d31c63c1dd1743c845e6497a4b45dc223a290565e669060d8086df1aeff28674021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 297b571346c2917d733e12a7bd9a4ed5054eefca0c966449f104ff3fd62cfaa2 0.600000000000 1562438 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": 1087837, "vin": [ { "gen": { "height": 1087827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "297b571346c2917d733e12a7bd9a4ed5054eefca0c966449f104ff3fd62cfaa2" } } ], "extra": [ 1, 211, 28, 99, 193, 221, 23, 67, 200, 69, 230, 73, 122, 75, 69, 220, 34, 58, 41, 5, 101, 230, 105, 6, 13, 128, 134, 223, 26, 239, 242, 134, 116, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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