Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65fc1d03b86a9dce71e5248ae2a6bdf10bc58cd12cbeec1028ed241b3cd90b9a

Tx prefix hash: 3dadcdd8ae8b33f55dbed12713ac8006567e19bb607c62f52524dfccc6a7a0df
Tx public key: e657dcfabf10b54df6558cfe598a1bbeae91781ccb48a36dee968a76a6cdc953
Timestamp: 1759679872 Timestamp [UCT]: 2025-10-05 15:57:52 Age [y:d:h:m:s]: 00:088:04:12:14
Block: 1383398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63147 RingCT/type: yes/0
Extra: 01e657dcfabf10b54df6558cfe598a1bbeae91781ccb48a36dee968a76a6cdc953021100000003a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d670043f9c953f8fd3c4f15be9c0887b34f8684b4265d4343eaf02369820691 0.600000000000 1871543 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": 1383408, "vin": [ { "gen": { "height": 1383398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d670043f9c953f8fd3c4f15be9c0887b34f8684b4265d4343eaf02369820691" } } ], "extra": [ 1, 230, 87, 220, 250, 191, 16, 181, 77, 246, 85, 140, 254, 89, 138, 27, 190, 174, 145, 120, 28, 203, 72, 163, 109, 238, 150, 138, 118, 166, 205, 201, 83, 2, 17, 0, 0, 0, 3, 165, 220, 205, 121, 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