Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a4549ef0dd5ce17b6b0ca18161859e330a4214efd9f49d1305676cd1d2d47d9

Tx prefix hash: 4418b0b882b0eada582b03f69eea797e6501899cf75ba86395167a65792b5c79
Tx public key: 2c6f1e67a8ee588095eb9909a6d677b9293bc313adfd5df1fba89dc3d8240154
Timestamp: 1763105014 Timestamp [UCT]: 2025-11-14 07:23:34 Age [y:d:h:m:s]: 00:055:22:36:28
Block: 1411799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40051 RingCT/type: yes/0
Extra: 012c6f1e67a8ee588095eb9909a6d677b9293bc313adfd5df1fba89dc3d82401540211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a09be4761ea7a8650b784e54598c9fc6d5753eeea87cfa11f36dd378c76c27e 0.600000000000 1900262 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": 1411809, "vin": [ { "gen": { "height": 1411799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a09be4761ea7a8650b784e54598c9fc6d5753eeea87cfa11f36dd378c76c27e" } } ], "extra": [ 1, 44, 111, 30, 103, 168, 238, 88, 128, 149, 235, 153, 9, 166, 214, 119, 185, 41, 59, 195, 19, 173, 253, 93, 241, 251, 168, 157, 195, 216, 36, 1, 84, 2, 17, 0, 0, 0, 2, 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