Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c894304f29a63bf5c039a644550f5dd366f1a72c2c4521aec6c659d9468c30f

Tx prefix hash: 16f426b970333d6671613b3eefb14410cd01ead014d05e79616ab315cf3b7fce
Tx public key: ccb17794139c04ba56edaad19db0f0341fb833e3ea9c0e3d11b0c8f0d6634567
Timestamp: 1763454634 Timestamp [UCT]: 2025-11-18 08:30:34 Age [y:d:h:m:s]: 00:010:00:51:00
Block: 1414689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7188 RingCT/type: yes/0
Extra: 01ccb17794139c04ba56edaad19db0f0341fb833e3ea9c0e3d11b0c8f0d663456702110000000343b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b218228c26c919198032cf67a71d17dc9ea7d9bc0e7da1ae4036183b6cc52581 0.600000000000 1903180 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": 1414699, "vin": [ { "gen": { "height": 1414689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b218228c26c919198032cf67a71d17dc9ea7d9bc0e7da1ae4036183b6cc52581" } } ], "extra": [ 1, 204, 177, 119, 148, 19, 156, 4, 186, 86, 237, 170, 209, 157, 176, 240, 52, 31, 184, 51, 227, 234, 156, 14, 61, 17, 176, 200, 240, 214, 99, 69, 103, 2, 17, 0, 0, 0, 3, 67, 181, 4, 113, 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