Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbef63271c309b8cbbc60f62b53269d9b563fcc7c8433eabdcc93a789388543a

Tx prefix hash: 09b85421472e9057ff0432b5e596255529ea54b0f176762ff35d99b273bd1dc7
Tx public key: 22127ef7441a29704ee4547a3dcf427a8b0e36ee1fa6c4a424b845c6cca6ff24
Timestamp: 1722784234 Timestamp [UCT]: 2024-08-04 15:10:34 Age [y:d:h:m:s]: 00:100:22:16:19
Block: 1080636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72214 RingCT/type: yes/0
Extra: 0122127ef7441a29704ee4547a3dcf427a8b0e36ee1fa6c4a424b845c6cca6ff2402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 526a6b2e99e5f5dbff99485af98bc6b9a595228e6ae284ae2b7f07fd2ff2c043 0.600000000000 1554075 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": 1080646, "vin": [ { "gen": { "height": 1080636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "526a6b2e99e5f5dbff99485af98bc6b9a595228e6ae284ae2b7f07fd2ff2c043" } } ], "extra": [ 1, 34, 18, 126, 247, 68, 26, 41, 112, 78, 228, 84, 122, 61, 207, 66, 122, 139, 14, 54, 238, 31, 166, 196, 164, 36, 184, 69, 198, 204, 166, 255, 36, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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