Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6d04012898fbba367017e149d9e004610b7d22019d2e1d88d369e5c10d0f03c

Tx prefix hash: b8577ebdec3beadfba6a79401303c0ab84e265f573368af174aa9cb1415b0447
Tx public key: 1fe0e93f399f5d3a10bfd460836ef9954cb1c9e842d1e1dc692dad3071e5ca5a
Timestamp: 1721778912 Timestamp [UCT]: 2024-07-23 23:55:12 Age [y:d:h:m:s]: 01:108:00:44:26
Block: 1072297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335710 RingCT/type: yes/0
Extra: 011fe0e93f399f5d3a10bfd460836ef9954cb1c9e842d1e1dc692dad3071e5ca5a021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3aa7e7c9c2bd8d084c25d71bd39f9da1513dcefc33d8aa4fe9e0c29d6820a91c 0.600000000000 1544758 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": 1072307, "vin": [ { "gen": { "height": 1072297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3aa7e7c9c2bd8d084c25d71bd39f9da1513dcefc33d8aa4fe9e0c29d6820a91c" } } ], "extra": [ 1, 31, 224, 233, 63, 57, 159, 93, 58, 16, 191, 212, 96, 131, 110, 249, 149, 76, 177, 201, 232, 66, 209, 225, 220, 105, 45, 173, 48, 113, 229, 202, 90, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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