Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a11e1e16c1552012aaa1c16eb07815a9375d776870541ded0e2895194536d5d6

Tx prefix hash: 395143ad142fc0485c959ac3f11472de352f761ca9af61ac93b907b82711e172
Tx public key: c8c5c58a6f611b683c4d329fb955c4a1c6282b2f9913f0301bcd464ddb7043d4
Timestamp: 1760833504 Timestamp [UCT]: 2025-10-19 00:25:04 Age [y:d:h:m:s]: 00:029:12:50:35
Block: 1392983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21131 RingCT/type: yes/0
Extra: 01c8c5c58a6f611b683c4d329fb955c4a1c6282b2f9913f0301bcd464ddb7043d40211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c30f1fed160ae7ffc95200f5c4dd1a9090d63645a1b2d99742e348299f21a4a3 0.600000000000 1881240 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": 1392993, "vin": [ { "gen": { "height": 1392983 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c30f1fed160ae7ffc95200f5c4dd1a9090d63645a1b2d99742e348299f21a4a3" } } ], "extra": [ 1, 200, 197, 197, 138, 111, 97, 27, 104, 60, 77, 50, 159, 185, 85, 196, 161, 198, 40, 43, 47, 153, 19, 240, 48, 27, 205, 70, 77, 219, 112, 67, 212, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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