Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2effd7472bfdcf1505b07a776f049da089bc9066315b2c9b3d11473ab5ccc20

Tx prefix hash: 800238f1c4b6163dc81474bed84ef4b6e990a90d6f11120ae901804d14476b9e
Tx public key: 09d97fd0b841533e97f70ad578baa4cab098c62cbaca02d51d0a9cf870e35e80
Timestamp: 1709726277 Timestamp [UCT]: 2024-03-06 11:57:57 Age [y:d:h:m:s]: 00:355:17:59:58
Block: 972392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254343 RingCT/type: yes/0
Extra: 0109d97fd0b841533e97f70ad578baa4cab098c62cbaca02d51d0a9cf870e35e8002110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73dc99d14d907c162736040471ab12f3df706f8a92f45c241a2dd49fb1d720c1 0.600000000000 1432303 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": 972402, "vin": [ { "gen": { "height": 972392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73dc99d14d907c162736040471ab12f3df706f8a92f45c241a2dd49fb1d720c1" } } ], "extra": [ 1, 9, 217, 127, 208, 184, 65, 83, 62, 151, 247, 10, 213, 120, 186, 164, 202, 176, 152, 198, 44, 186, 202, 2, 213, 29, 10, 156, 248, 112, 227, 94, 128, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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