Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 667eeae1fab9d6d8518c88321c7f877fdd2e241cf0e6e76e1afac4e1fb0534fd

Tx prefix hash: 9b218e28010ad862b6d9b37ed65e23da847fab9673a741187459267d3be4619f
Tx public key: a002f2caca44f4ae30d049ab32dd7699e0e4953bb29a29f850af2c7acfbea78b
Timestamp: 1736103995 Timestamp [UCT]: 2025-01-05 19:06:35 Age [y:d:h:m:s]: 00:311:17:19:29
Block: 1190927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220300 RingCT/type: yes/0
Extra: 01a002f2caca44f4ae30d049ab32dd7699e0e4953bb29a29f850af2c7acfbea78b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 261c5f3cd42e1c1bb8ac623751a420341748230d75df3f0e06b2024e24dea123 0.600000000000 1677450 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": 1190937, "vin": [ { "gen": { "height": 1190927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "261c5f3cd42e1c1bb8ac623751a420341748230d75df3f0e06b2024e24dea123" } } ], "extra": [ 1, 160, 2, 242, 202, 202, 68, 244, 174, 48, 208, 73, 171, 50, 221, 118, 153, 224, 228, 149, 59, 178, 154, 41, 248, 80, 175, 44, 122, 207, 190, 167, 139, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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