Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55a5022ebe56ae7610f7a54886c09f316ae825b27e87a21bee2929f1c53353cd

Tx prefix hash: b550514cc99e046b16f9e7300c7045a89fae5461d2166de378e09a85a4712690
Tx public key: f73a40becdd1ee7b01fb8b208caee919fc505dd4f30b0eba6bbbe8d03b20f140
Timestamp: 1753220652 Timestamp [UCT]: 2025-07-22 21:44:12 Age [y:d:h:m:s]: 00:083:00:03:21
Block: 1331223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58103 RingCT/type: yes/0
Extra: 01f73a40becdd1ee7b01fb8b208caee919fc505dd4f30b0eba6bbbe8d03b20f140021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77e6e56d610ae79fecf52f9ae9c6b533e02e2768ae7efd4c964630572cdce18c 0.600000000000 1819018 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": 1331233, "vin": [ { "gen": { "height": 1331223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77e6e56d610ae79fecf52f9ae9c6b533e02e2768ae7efd4c964630572cdce18c" } } ], "extra": [ 1, 247, 58, 64, 190, 205, 209, 238, 123, 1, 251, 139, 32, 140, 174, 233, 25, 252, 80, 93, 212, 243, 11, 14, 186, 107, 187, 232, 208, 59, 32, 241, 64, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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