Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8673e873b7d58b81118036fa1602e79d87a1d7606adae000cce00039ce262c65

Tx prefix hash: 82713ebddd517db45c31a35e0bde6c20a9edeb01de120bad623bb4376a5d9c3e
Tx public key: 985e8894d2fae6b8f9c2b81216464a9b468e58fd0b04cc59dbd3da0c7dd82d67
Timestamp: 1720048674 Timestamp [UCT]: 2024-07-03 23:17:54 Age [y:d:h:m:s]: 00:273:00:27:01
Block: 1057951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195067 RingCT/type: yes/0
Extra: 01985e8894d2fae6b8f9c2b81216464a9b468e58fd0b04cc59dbd3da0c7dd82d6702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 555117690dd24cc3e27632e4e80079bfd9962b49acbd7b4f9b5c4febf2ffa4b2 0.600000000000 1528394 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": 1057961, "vin": [ { "gen": { "height": 1057951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "555117690dd24cc3e27632e4e80079bfd9962b49acbd7b4f9b5c4febf2ffa4b2" } } ], "extra": [ 1, 152, 94, 136, 148, 210, 250, 230, 184, 249, 194, 184, 18, 22, 70, 74, 155, 70, 142, 88, 253, 11, 4, 204, 89, 219, 211, 218, 12, 125, 216, 45, 103, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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