Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbf7200f09bb7e19b5b229a379650a9066d18a14b58a4703bc1cca4da6e54c81

Tx prefix hash: b85add54b21288ed0b9c2efb643d8a1c760d52c53162d3f57ed81a88194ac830
Tx public key: f79da429e7264d44f9b1279b4c30d9ae23605c08558b17cee47ac985e48d7a11
Timestamp: 1753970858 Timestamp [UCT]: 2025-07-31 14:07:38 Age [y:d:h:m:s]: 00:021:04:25:43
Block: 1337376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14072 RingCT/type: yes/0
Extra: 01f79da429e7264d44f9b1279b4c30d9ae23605c08558b17cee47ac985e48d7a11021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e9388bebe8b8575463cc9cc2490a8a26384d9a3413af97d3015fac4f491d6e4 0.600000000000 1825181 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": 1337386, "vin": [ { "gen": { "height": 1337376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e9388bebe8b8575463cc9cc2490a8a26384d9a3413af97d3015fac4f491d6e4" } } ], "extra": [ 1, 247, 157, 164, 41, 231, 38, 77, 68, 249, 177, 39, 155, 76, 48, 217, 174, 35, 96, 92, 8, 85, 139, 23, 206, 228, 122, 201, 133, 228, 141, 122, 17, 2, 17, 0, 0, 0, 4, 216, 231, 210, 65, 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