Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a9be8beeecd144ab1896c76b9e9261386d662693f1dcf8ec20f7e33392a1e16

Tx prefix hash: 8b270e43674ee99c7e40171afa28105de2fd8c8e5393640ae832479b88e0764f
Tx public key: 8c6a5b466ae29f17d9932d7c7818c65ce04f489b06b5e2f1637b44994c700bb9
Timestamp: 1751324492 Timestamp [UCT]: 2025-06-30 23:01:32 Age [y:d:h:m:s]: 00:143:18:49:19
Block: 1316154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100951 RingCT/type: yes/0
Extra: 018c6a5b466ae29f17d9932d7c7818c65ce04f489b06b5e2f1637b44994c700bb9021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fa4aabdcff0105be877f78a94ebaf8b78a53fbc014d4e363738f245c59e33c6 0.600000000000 1803811 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": 1316164, "vin": [ { "gen": { "height": 1316154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fa4aabdcff0105be877f78a94ebaf8b78a53fbc014d4e363738f245c59e33c6" } } ], "extra": [ 1, 140, 106, 91, 70, 106, 226, 159, 23, 217, 147, 45, 124, 120, 24, 198, 92, 224, 79, 72, 155, 6, 181, 226, 241, 99, 123, 68, 153, 76, 112, 11, 185, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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