Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62632876b0c3b6f795db197034169719a2c9db90dea3290baa821f3e0b1fb136

Tx prefix hash: de094a3c916950693a102478fce7a49b12b1d42a9ad24b2cfd79089e3390edc1
Tx public key: c8031b353f89e1095b3946fddf1a906e5fe55b10ec7e9538e1a857f69d7512bf
Timestamp: 1733815176 Timestamp [UCT]: 2024-12-10 07:19:36 Age [y:d:h:m:s]: 00:120:14:54:26
Block: 1171991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85996 RingCT/type: yes/0
Extra: 01c8031b353f89e1095b3946fddf1a906e5fe55b10ec7e9538e1a857f69d7512bf021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b012f44d0cee77ca62d1f9d78dbfa46908f15423c1d6f49c89d86634ba6e44c 0.600000000000 1657824 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": 1172001, "vin": [ { "gen": { "height": 1171991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b012f44d0cee77ca62d1f9d78dbfa46908f15423c1d6f49c89d86634ba6e44c" } } ], "extra": [ 1, 200, 3, 27, 53, 63, 137, 225, 9, 91, 57, 70, 253, 223, 26, 144, 110, 95, 229, 91, 16, 236, 126, 149, 56, 225, 168, 87, 246, 157, 117, 18, 191, 2, 17, 0, 0, 0, 2, 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