Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e87e60c3f2e27e503c6668349f4eef00737cfca96269f335ad610cd55005e4f5

Tx prefix hash: 5a49bc5ff9495848d92c38d0d5334f344bc81e0d85b6270c4bbb6bf18fea93c7
Tx public key: e23e976ef48ba2805dce63935053ac96a940083c5ddbf328e6d85380fdcc8e6f
Timestamp: 1733334689 Timestamp [UCT]: 2024-12-04 17:51:29 Age [y:d:h:m:s]: 00:199:19:43:52
Block: 1168008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142469 RingCT/type: yes/0
Extra: 01e23e976ef48ba2805dce63935053ac96a940083c5ddbf328e6d85380fdcc8e6f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35cb82f3f41b1efcc698a11a08d34ee5f9c9d574d9f5f988e0b29bb0bb0e0217 0.600000000000 1653715 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": 1168018, "vin": [ { "gen": { "height": 1168008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35cb82f3f41b1efcc698a11a08d34ee5f9c9d574d9f5f988e0b29bb0bb0e0217" } } ], "extra": [ 1, 226, 62, 151, 110, 244, 139, 162, 128, 93, 206, 99, 147, 80, 83, 172, 150, 169, 64, 8, 60, 93, 219, 243, 40, 230, 216, 83, 128, 253, 204, 142, 111, 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