Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d69223421614e68f5cbb35bdbf38645ec7a8c32ec9d375e11ecfc07395fe0a53

Tx prefix hash: 742a32704f7db69d5c970d1398b17a4dd5b18448579e2f3cc8a8d3af9b06c80a
Tx public key: 16cb8e66e28d88a5671cc114c6a0b4600e7c77bf68b8ffb6ac59e69bff5e60f9
Timestamp: 1727678368 Timestamp [UCT]: 2024-09-30 06:39:28 Age [y:d:h:m:s]: 00:114:17:19:13
Block: 1121212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81985 RingCT/type: yes/0
Extra: 0116cb8e66e28d88a5671cc114c6a0b4600e7c77bf68b8ffb6ac59e69bff5e60f9021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e7953669ab07b7db5a9c8a133d6422a0c40476672b7321a966669142e297249 0.600000000000 1603407 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": 1121222, "vin": [ { "gen": { "height": 1121212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e7953669ab07b7db5a9c8a133d6422a0c40476672b7321a966669142e297249" } } ], "extra": [ 1, 22, 203, 142, 102, 226, 141, 136, 165, 103, 28, 193, 20, 198, 160, 180, 96, 14, 124, 119, 191, 104, 184, 255, 182, 172, 89, 230, 155, 255, 94, 96, 249, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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