Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd0f64ee74f6dd7811322d0a0a9d57ace983478590dbcc68d75a3900e65906ec

Tx prefix hash: 6403c45b3e2531d9e4bba788a91a31579dad10e41820772c66e1585a8845c1a5
Tx public key: e53b6ac96fcd2844479947433a0a226cd209b55d4c37152f4230da7d31eb46f5
Timestamp: 1718368106 Timestamp [UCT]: 2024-06-14 12:28:26 Age [y:d:h:m:s]: 00:257:18:34:18
Block: 1044037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184155 RingCT/type: yes/0
Extra: 01e53b6ac96fcd2844479947433a0a226cd209b55d4c37152f4230da7d31eb46f50211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abf192fb16bca71f35d9d8a03b8b7ea7e6c2a0123ebd59eed928e87beac718d7 0.600000000000 1513234 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": 1044047, "vin": [ { "gen": { "height": 1044037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abf192fb16bca71f35d9d8a03b8b7ea7e6c2a0123ebd59eed928e87beac718d7" } } ], "extra": [ 1, 229, 59, 106, 201, 111, 205, 40, 68, 71, 153, 71, 67, 58, 10, 34, 108, 210, 9, 181, 93, 76, 55, 21, 47, 66, 48, 218, 125, 49, 235, 70, 245, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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