Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd78f810f7be9a41efc11d3bdbac5b8f443faa9a84e37aac99586d98271a33a5

Tx prefix hash: 44a5a336542c7ed0f139f3d17122b0ca063ebb5a884bbdf13c9bfa158ddaadc4
Tx public key: fa6e91b5556a6197f05cc437f9f46a43f8be5bc2c939902743599b5961b42f0b
Timestamp: 1760294021 Timestamp [UCT]: 2025-10-12 18:33:41 Age [y:d:h:m:s]: 00:109:08:00:51
Block: 1388498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78113 RingCT/type: yes/0
Extra: 01fa6e91b5556a6197f05cc437f9f46a43f8be5bc2c939902743599b5961b42f0b021100000001719c6d43000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 057f7c732380b5783dc0d9e0a47a11d232f070410db5f555d5f211a10581e15b 0.600000000000 1876711 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": 1388508, "vin": [ { "gen": { "height": 1388498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "057f7c732380b5783dc0d9e0a47a11d232f070410db5f555d5f211a10581e15b" } } ], "extra": [ 1, 250, 110, 145, 181, 85, 106, 97, 151, 240, 92, 196, 55, 249, 244, 106, 67, 248, 190, 91, 194, 201, 57, 144, 39, 67, 89, 155, 89, 97, 180, 47, 11, 2, 17, 0, 0, 0, 1, 113, 156, 109, 67, 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