Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 040ea03736e5fd69b89b3be90559423a447d774c327de6de2440d497746471ad

Tx prefix hash: 5e8772640cf327fac80be918f2101befe7b000f49a1d84d84c5616542d6e161b
Tx public key: 8c37a002b6295f81e47f0023f7a18e31dea0bd8f3aa7647a9fc5763468202f19
Timestamp: 1713477698 Timestamp [UCT]: 2024-04-18 22:01:38 Age [y:d:h:m:s]: 01:198:04:01:54
Block: 1003478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400269 RingCT/type: yes/0
Extra: 018c37a002b6295f81e47f0023f7a18e31dea0bd8f3aa7647a9fc5763468202f1902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d35c10d6febce7b7f4f67c739bef652b1f89614ae8463e4d9a227a8a029814d2 0.600000000000 1464020 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": 1003488, "vin": [ { "gen": { "height": 1003478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d35c10d6febce7b7f4f67c739bef652b1f89614ae8463e4d9a227a8a029814d2" } } ], "extra": [ 1, 140, 55, 160, 2, 182, 41, 95, 129, 228, 127, 0, 35, 247, 161, 142, 49, 222, 160, 189, 143, 58, 167, 100, 122, 159, 197, 118, 52, 104, 32, 47, 25, 2, 17, 0, 0, 0, 1, 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