Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3043b266c131d45d39a8dcb25311309bf9441bd0c5c6cca6e7c7096e14386ba9

Tx prefix hash: 159b2360ca0e65cfebf7d2246c0ff24c706d1be8232232089c4bb585236e5acf
Tx public key: 388cac9a6af06b98b549fb01c979884521b0c428b5873f1c42e7070a6f14354a
Timestamp: 1737812791 Timestamp [UCT]: 2025-01-25 13:46:31 Age [y:d:h:m:s]: 00:146:13:23:24
Block: 1205035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104442 RingCT/type: yes/0
Extra: 01388cac9a6af06b98b549fb01c979884521b0c428b5873f1c42e7070a6f14354a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43d20c59a297b8b1dfd486b8138bd732ae11ae98ca97ba7225bd2bf43e66c0a9 0.600000000000 1691732 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": 1205045, "vin": [ { "gen": { "height": 1205035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43d20c59a297b8b1dfd486b8138bd732ae11ae98ca97ba7225bd2bf43e66c0a9" } } ], "extra": [ 1, 56, 140, 172, 154, 106, 240, 107, 152, 181, 73, 251, 1, 201, 121, 136, 69, 33, 176, 196, 40, 181, 135, 63, 28, 66, 231, 7, 10, 111, 20, 53, 74, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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