Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6433589f34ed795d40ef560eec95af2e75550c68bbe586befe695c8fce994908

Tx prefix hash: 960c835b4b9776302d6cb189b63c6e2544ea34eb1e5ed829f629457898ebe668
Tx public key: 0f5229910c1c4e3d93a2410e532ab43d0a7b07acadce32a71c7dfde0de40fd77
Timestamp: 1713507683 Timestamp [UCT]: 2024-04-19 06:21:23 Age [y:d:h:m:s]: 00:311:23:33:26
Block: 1003725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223009 RingCT/type: yes/0
Extra: 010f5229910c1c4e3d93a2410e532ab43d0a7b07acadce32a71c7dfde0de40fd77021100000004e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b548053bfa07d77924ab944f86cdbc54abd0293c6aef6ae9e2cd5e90776dc945 0.600000000000 1464267 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": 1003735, "vin": [ { "gen": { "height": 1003725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b548053bfa07d77924ab944f86cdbc54abd0293c6aef6ae9e2cd5e90776dc945" } } ], "extra": [ 1, 15, 82, 41, 145, 12, 28, 78, 61, 147, 162, 65, 14, 83, 42, 180, 61, 10, 123, 7, 172, 173, 206, 50, 167, 28, 125, 253, 224, 222, 64, 253, 119, 2, 17, 0, 0, 0, 4, 228, 187, 107, 131, 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