Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 965a505c6b409b3a2f288570fbfc60a834daac184c993376cde89ff65b3ef7db

Tx prefix hash: a5ecec92250cfa3d433e082c8964568bffbb50b734803b76a5d5384cdff0b908
Tx public key: a047e030bc9a46fb4843d3465e9b07f06dcbb1cc6f5c128c6da36b5fcf5bf458
Timestamp: 1740057520 Timestamp [UCT]: 2025-02-20 13:18:40 Age [y:d:h:m:s]: 00:306:05:41:26
Block: 1223379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216669 RingCT/type: yes/0
Extra: 01a047e030bc9a46fb4843d3465e9b07f06dcbb1cc6f5c128c6da36b5fcf5bf45802110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba285048a894625fed1072ed03a7bb1174321eb042a34284325a18afec1f524b 0.600000000000 1710236 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": 1223389, "vin": [ { "gen": { "height": 1223379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba285048a894625fed1072ed03a7bb1174321eb042a34284325a18afec1f524b" } } ], "extra": [ 1, 160, 71, 224, 48, 188, 154, 70, 251, 72, 67, 211, 70, 94, 155, 7, 240, 109, 203, 177, 204, 111, 92, 18, 140, 109, 163, 107, 95, 207, 91, 244, 88, 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