Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad0c7ee3389bd3ea7bd01dc12920b35d441428b329fe4b6897ca65bfdfe09105

Tx prefix hash: 7f9034223c28ad0c3ca8018bd264151dc925af5ef32690c81716677fdbb1a734
Tx public key: 77d8e94e623c33ef134e7470352f82cbf1c7e3a93e34168fe0fb37aa1bc6f644
Timestamp: 1709854113 Timestamp [UCT]: 2024-03-07 23:28:33 Age [y:d:h:m:s]: 01:075:15:14:15
Block: 973456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315082 RingCT/type: yes/0
Extra: 0177d8e94e623c33ef134e7470352f82cbf1c7e3a93e34168fe0fb37aa1bc6f64402110000000646812bb8000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abd6665dddc4a8c0bca059a64b5f5b795a9eb5ac8ae8c4ef2ff3a77756f3167a 0.600000000000 1433391 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": 973466, "vin": [ { "gen": { "height": 973456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abd6665dddc4a8c0bca059a64b5f5b795a9eb5ac8ae8c4ef2ff3a77756f3167a" } } ], "extra": [ 1, 119, 216, 233, 78, 98, 60, 51, 239, 19, 78, 116, 112, 53, 47, 130, 203, 241, 199, 227, 169, 62, 52, 22, 143, 224, 251, 55, 170, 27, 198, 246, 68, 2, 17, 0, 0, 0, 6, 70, 129, 43, 184, 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