Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c518107661cd6f07a059d6d505bbc0ef462a68b9bd3d213a61cdcdcf76e3c7d0

Tx prefix hash: 578107ca840af45db0fed57687796eb13b772ca1fbc4cb8a3b10a6498f781466
Tx public key: a35f30d1dbd677fc4125e682f9303aa88c743e414f68f4afa6fbfcb9d82f15a5
Timestamp: 1751541635 Timestamp [UCT]: 2025-07-03 11:20:35 Age [y:d:h:m:s]: 00:137:10:04:37
Block: 1317900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96459 RingCT/type: yes/0
Extra: 01a35f30d1dbd677fc4125e682f9303aa88c743e414f68f4afa6fbfcb9d82f15a502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 808d09c509286779fc05927524c7e6ea48e3530be651104e6e8fac6ca2bb2ebc 0.600000000000 1805571 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": 1317910, "vin": [ { "gen": { "height": 1317900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "808d09c509286779fc05927524c7e6ea48e3530be651104e6e8fac6ca2bb2ebc" } } ], "extra": [ 1, 163, 95, 48, 209, 219, 214, 119, 252, 65, 37, 230, 130, 249, 48, 58, 168, 140, 116, 62, 65, 79, 104, 244, 175, 166, 251, 252, 185, 216, 47, 21, 165, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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