Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f905049e58fe046e4c4a02cbad168ccee2cdcf981204b682fbf805203123a22e

Tx prefix hash: 29ba60bcb29a167741f492d00d4fec0ad78e88c6cdfb7f363221b32c7e901d7b
Tx public key: d1c8f22cac73d291f7b0e53053585e96b3ce10dc3762ab18a7b85f137d26cb9e
Timestamp: 1765344122 Timestamp [UCT]: 2025-12-10 05:22:02 Age [y:d:h:m:s]: 00:029:10:57:48
Block: 1430345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21095 RingCT/type: yes/0
Extra: 01d1c8f22cac73d291f7b0e53053585e96b3ce10dc3762ab18a7b85f137d26cb9e021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f485851b93421ce5790e2259d20996012b49fbfacb6469256cd8a30395c45dc2 0.600000000000 1919094 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": 1430355, "vin": [ { "gen": { "height": 1430345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f485851b93421ce5790e2259d20996012b49fbfacb6469256cd8a30395c45dc2" } } ], "extra": [ 1, 209, 200, 242, 44, 172, 115, 210, 145, 247, 176, 229, 48, 83, 88, 94, 150, 179, 206, 16, 220, 55, 98, 171, 24, 167, 184, 95, 19, 125, 38, 203, 158, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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