Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d26facfb67b67d4b3009aa0639059a7b6d391d4e04c1b09048c05077f554d52

Tx prefix hash: 9135ef6b3345efa676ed0bed0877bca0e221d0a1a0890da35f5fa3d760a42177
Tx public key: 081404be2c26837367ef8293f3c8448736f8a316d217e363c1f68b525aba919e
Timestamp: 1708064925 Timestamp [UCT]: 2024-02-16 06:28:45 Age [y:d:h:m:s]: 01:044:18:29:30
Block: 958607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293024 RingCT/type: yes/0
Extra: 01081404be2c26837367ef8293f3c8448736f8a316d217e363c1f68b525aba919e02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5273976deda78d7c2e4e33a95fd18f1a12dd4e2ba4a9603ab2e2fe8333cd268 0.600000000000 1417966 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": 958617, "vin": [ { "gen": { "height": 958607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5273976deda78d7c2e4e33a95fd18f1a12dd4e2ba4a9603ab2e2fe8333cd268" } } ], "extra": [ 1, 8, 20, 4, 190, 44, 38, 131, 115, 103, 239, 130, 147, 243, 200, 68, 135, 54, 248, 163, 22, 210, 23, 227, 99, 193, 246, 139, 82, 90, 186, 145, 158, 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