Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42264dc86dfb9504acb83a1167a83b6baf789c63e326a2639f68b564c5e1f134

Tx prefix hash: 676d46c6cc8f3bb6603ca6f6e24e5f23b69ce023b61a2298e14eeac1193dc4ca
Tx public key: b3ab01e14fedfee5efdf5ee3eb67f9838cc10147d495bd6cdc7e3a55c19758ad
Timestamp: 1734010463 Timestamp [UCT]: 2024-12-12 13:34:23 Age [y:d:h:m:s]: 00:186:21:40:36
Block: 1173620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133299 RingCT/type: yes/0
Extra: 01b3ab01e14fedfee5efdf5ee3eb67f9838cc10147d495bd6cdc7e3a55c19758ad021100000001a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa8dd833ed905974eda3365dfd28183a68c7d330982afd62b9bcb25d626dd045 0.600000000000 1659663 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": 1173630, "vin": [ { "gen": { "height": 1173620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa8dd833ed905974eda3365dfd28183a68c7d330982afd62b9bcb25d626dd045" } } ], "extra": [ 1, 179, 171, 1, 225, 79, 237, 254, 229, 239, 223, 94, 227, 235, 103, 249, 131, 140, 193, 1, 71, 212, 149, 189, 108, 220, 126, 58, 85, 193, 151, 88, 173, 2, 17, 0, 0, 0, 1, 162, 215, 95, 68, 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