Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0333e4ef83c4aef79d47bc2be72545885c2852094ef24f2ba3b640acc12d176e

Tx prefix hash: 0dca16321c14d29d64d8ffd0788ce9a9a43e9a65f0c6336a48e8e4f19fc01bac
Tx public key: e61dfd3f71ab05595e1081c2dcc19556e4294457909d3d6d5021a3890f9a5542
Timestamp: 1705020889 Timestamp [UCT]: 2024-01-12 00:54:49 Age [y:d:h:m:s]: 01:327:14:40:46
Block: 933359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493015 RingCT/type: yes/0
Extra: 01e61dfd3f71ab05595e1081c2dcc19556e4294457909d3d6d5021a3890f9a55420211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 435b4b221c0a9d11252c59d023ad3546dd56f1551fd344dc25764393d8ae0077 0.600000000000 1391321 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": 933369, "vin": [ { "gen": { "height": 933359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "435b4b221c0a9d11252c59d023ad3546dd56f1551fd344dc25764393d8ae0077" } } ], "extra": [ 1, 230, 29, 253, 63, 113, 171, 5, 89, 94, 16, 129, 194, 220, 193, 149, 86, 228, 41, 68, 87, 144, 157, 61, 109, 80, 33, 163, 137, 15, 154, 85, 66, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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