Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d690c10b899165b4e1d5e6cd2a7161961ddf16d6592974d6b09d797bacc8359

Tx prefix hash: b0fe145b9e13f04e6e97d64fbf5bdcf5e06a87adb71d6d775756d0db74097c6a
Tx public key: 468d96dc02247d4d3f4205e5f4f0375b8aed32127430ffc3848811316a39db15
Timestamp: 1713110342 Timestamp [UCT]: 2024-04-14 15:59:02 Age [y:d:h:m:s]: 00:357:19:26:10
Block: 1000415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255818 RingCT/type: yes/0
Extra: 01468d96dc02247d4d3f4205e5f4f0375b8aed32127430ffc3848811316a39db1502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9dede5aa57750d0f24d4912f4cf7ecdaf6d022fb662bf17aee1f64e8a262ef72 0.600000000000 1460913 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": 1000425, "vin": [ { "gen": { "height": 1000415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9dede5aa57750d0f24d4912f4cf7ecdaf6d022fb662bf17aee1f64e8a262ef72" } } ], "extra": [ 1, 70, 141, 150, 220, 2, 36, 125, 77, 63, 66, 5, 229, 244, 240, 55, 91, 138, 237, 50, 18, 116, 48, 255, 195, 132, 136, 17, 49, 106, 57, 219, 21, 2, 17, 0, 0, 0, 2, 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