Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea82cddeeee69098ad43ef37197319caf1206a9f953fe774f541895d6ba919e2

Tx prefix hash: 16812bb9c5692f6e6df8c49c02872d25a76bb6a2b4b3be9025b65b5ed3f3d51e
Tx public key: 818e78c232d1d9315a849560aeaa5422d37d9e9ff280c9f29241e0f281388849
Timestamp: 1765962451 Timestamp [UCT]: 2025-12-17 09:07:31 Age [y:d:h:m:s]: 00:004:02:39:43
Block: 1435465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2943 RingCT/type: yes/0
Extra: 01818e78c232d1d9315a849560aeaa5422d37d9e9ff280c9f29241e0f2813888490211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6089621d39fc7a1575293b6c4c209c4bbc71c6730a5e066279a0f716c86effa0 0.600000000000 1924262 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": 1435475, "vin": [ { "gen": { "height": 1435465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6089621d39fc7a1575293b6c4c209c4bbc71c6730a5e066279a0f716c86effa0" } } ], "extra": [ 1, 129, 142, 120, 194, 50, 209, 217, 49, 90, 132, 149, 96, 174, 170, 84, 34, 211, 125, 158, 159, 242, 128, 201, 242, 146, 65, 224, 242, 129, 56, 136, 73, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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