Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa9c90374912c1eda4b5a63b04b1568f00c9d3d439e0646bba520789d0c93bac

Tx prefix hash: ba19a881cd35f67245269f51d09a82442a037f5c0722a4760918155cc175c6f1
Tx public key: cd440901777eb0a59b1e7ea9b9d7205d26816dfe5c0cc1c07a54f30d294281b6
Timestamp: 1764800615 Timestamp [UCT]: 2025-12-03 22:23:35 Age [y:d:h:m:s]: 00:018:10:26:27
Block: 1425843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13194 RingCT/type: yes/0
Extra: 01cd440901777eb0a59b1e7ea9b9d7205d26816dfe5c0cc1c07a54f30d294281b6021100000003fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd191839e9a05b9e65110de4c08ea8476160367c375b1f806de6d464372e4d6e 0.600000000000 1914524 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": 1425853, "vin": [ { "gen": { "height": 1425843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd191839e9a05b9e65110de4c08ea8476160367c375b1f806de6d464372e4d6e" } } ], "extra": [ 1, 205, 68, 9, 1, 119, 126, 176, 165, 155, 30, 126, 169, 185, 215, 32, 93, 38, 129, 109, 254, 92, 12, 193, 192, 122, 84, 243, 13, 41, 66, 129, 182, 2, 17, 0, 0, 0, 3, 251, 143, 208, 137, 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