Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b39ef7582ea39d231e146e6c4a17986b21729c9ea420e3b2fe348e581ebdebc9

Tx prefix hash: 6be4cebfb21aa31233215a602d2b87754e99ff507e67511035442d18b02ac93d
Tx public key: 082e0138c799a807d13fa78e380dcaa68fbda2af4aa6edbd22c684680d8c5d6a
Timestamp: 1712592114 Timestamp [UCT]: 2024-04-08 16:01:54 Age [y:d:h:m:s]: 01:210:02:40:23
Block: 996105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408864 RingCT/type: yes/0
Extra: 01082e0138c799a807d13fa78e380dcaa68fbda2af4aa6edbd22c684680d8c5d6a02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7261464b1b1daad1e3c451cc4fd17b9bc39fee996c5549ce6bbc7656b79247c 0.600000000000 1456521 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": 996115, "vin": [ { "gen": { "height": 996105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7261464b1b1daad1e3c451cc4fd17b9bc39fee996c5549ce6bbc7656b79247c" } } ], "extra": [ 1, 8, 46, 1, 56, 199, 153, 168, 7, 209, 63, 167, 142, 56, 13, 202, 166, 143, 189, 162, 175, 74, 166, 237, 189, 34, 198, 132, 104, 13, 140, 93, 106, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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