Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 677c14a29ae41fd909d05761f69f525654c73915cbe1c8cb4a4b85b0839cbd86

Tx prefix hash: 1c9e0065711c527573bf8633762987944e3cf16c2932aab1fbf5a3e4eaacb8ac
Tx public key: d5ed5e33946d5c085c60d12c3b741324e08735fabd406bb03c99004a2372ce47
Timestamp: 1581688842 Timestamp [UCT]: 2020-02-14 14:00:42 Age [y:d:h:m:s]: 04:357:15:58:21
Block: 64878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1147563 RingCT/type: yes/0
Extra: 01d5ed5e33946d5c085c60d12c3b741324e08735fabd406bb03c99004a2372ce470211000000084ac5aa02000000000000000000

1 output(s) for total of 374.139072296000 dcy

stealth address amount amount idx
00: c683473b95dc7fa74423d033aa49d3ddc6d91d79a5b82f6fecaf2821e54897e2 374.139072296000 119722 of 0

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": 64888, "vin": [ { "gen": { "height": 64878 } } ], "vout": [ { "amount": 374139072296, "target": { "key": "c683473b95dc7fa74423d033aa49d3ddc6d91d79a5b82f6fecaf2821e54897e2" } } ], "extra": [ 1, 213, 237, 94, 51, 148, 109, 92, 8, 92, 96, 209, 44, 59, 116, 19, 36, 224, 135, 53, 250, 189, 64, 107, 176, 60, 153, 0, 74, 35, 114, 206, 71, 2, 17, 0, 0, 0, 8, 74, 197, 170, 2, 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