Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b67f22e62d20478f7a1dfbdcfff2c0f814d1a5c057f16fdf134525bc2778c7d5

Tx prefix hash: e22ca6182e866c938052bdc078170da67230c6c62510daf56a00237e6fcb2555
Tx public key: 5fdbf86541db3da399aeade88694ffd4b20755c13719d510a09db277d7dc6aa8
Timestamp: 1694508456 Timestamp [UCT]: 2023-09-12 08:47:36 Age [y:d:h:m:s]: 01:065:15:51:25
Block: 846401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308214 RingCT/type: yes/0
Extra: 015fdbf86541db3da399aeade88694ffd4b20755c13719d510a09db277d7dc6aa80211000000024b8f5122000000000000000000

1 output(s) for total of 0.962769206000 dcy

stealth address amount amount idx
00: 4a724a6dc6e7d2da998d59da28c1f2d3483c33a69f442125f8c711d04f8f34a2 0.962769206000 1299859 of 0

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": 846411, "vin": [ { "gen": { "height": 846401 } } ], "vout": [ { "amount": 962769206, "target": { "key": "4a724a6dc6e7d2da998d59da28c1f2d3483c33a69f442125f8c711d04f8f34a2" } } ], "extra": [ 1, 95, 219, 248, 101, 65, 219, 61, 163, 153, 174, 173, 232, 134, 148, 255, 212, 178, 7, 85, 193, 55, 25, 213, 16, 160, 157, 178, 119, 215, 220, 106, 168, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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