Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eca5090c61e8c6a5681116b59868d90df47f2a23b35dc0147835ffb23f285b01

Tx prefix hash: bc9a75703596201f663a1ff0820468249b7fb05f5799adfd6bc4ff849be38ff4
Tx public key: a02ec7fe5a2a803238bdba5f5480e50aba7705434c8283d08303d062b3ee4f91
Timestamp: 1762851993 Timestamp [UCT]: 2025-11-11 09:06:33 Age [y:d:h:m:s]: 00:042:13:25:15
Block: 1409694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30463 RingCT/type: yes/0
Extra: 01a02ec7fe5a2a803238bdba5f5480e50aba7705434c8283d08303d062b3ee4f91021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16720c89b9e5f5a8d2c35d49a708d52ea6fbb860aea6764b37629f823da19e0c 0.600000000000 1898141 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": 1409704, "vin": [ { "gen": { "height": 1409694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16720c89b9e5f5a8d2c35d49a708d52ea6fbb860aea6764b37629f823da19e0c" } } ], "extra": [ 1, 160, 46, 199, 254, 90, 42, 128, 50, 56, 189, 186, 95, 84, 128, 229, 10, 186, 119, 5, 67, 76, 130, 131, 208, 131, 3, 208, 98, 179, 238, 79, 145, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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