Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2851989e61423466f60f6b30320ce6a4696309d935227fc9028df15f649d36a0

Tx prefix hash: bfc9e66cf0b86c93b83aa550dec52d7706d897749644bf05f5989f567bb52e32
Tx public key: f330a9dc4aec24561e8df447d927e2f55a5ebb328b8fea9962df9fb1fecb55b1
Timestamp: 1733670798 Timestamp [UCT]: 2024-12-08 15:13:18 Age [y:d:h:m:s]: 00:110:10:58:01
Block: 1170804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78723 RingCT/type: yes/0
Extra: 01f330a9dc4aec24561e8df447d927e2f55a5ebb328b8fea9962df9fb1fecb55b10211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6c3826573d4778a4e7da579ebecce23f5c07b205b62cf9d8110e51bff88e425 0.600000000000 1656537 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": 1170814, "vin": [ { "gen": { "height": 1170804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6c3826573d4778a4e7da579ebecce23f5c07b205b62cf9d8110e51bff88e425" } } ], "extra": [ 1, 243, 48, 169, 220, 74, 236, 36, 86, 30, 141, 244, 71, 217, 39, 226, 245, 90, 94, 187, 50, 139, 143, 234, 153, 98, 223, 159, 177, 254, 203, 85, 177, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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