Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 779b3bd9f5b91b196c8503bd10b57b93d26598e78e0a2e0b9f0f544c958b0b73

Tx prefix hash: 868d1dd942750f4a82e8b66c90b6ee987bb719f17d31de1fcc660e022297fac8
Tx public key: 4e093176361ae750a2c8242e8d8bc78b3717142e0d3a742f695734fa075febae
Timestamp: 1580481435 Timestamp [UCT]: 2020-01-31 14:37:15 Age [y:d:h:m:s]: 05:033:17:57:43
Block: 55871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1175962 RingCT/type: yes/0
Extra: 014e093176361ae750a2c8242e8d8bc78b3717142e0d3a742f695734fa075febae021100000003ff58ae94000000000000000000

1 output(s) for total of 400.753208636000 dcy

stealth address amount amount idx
00: 44af16979d67a647fec19def20cc58a482015de6bb7fb31ba644842b312a5d43 400.753208636000 103065 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": 55881, "vin": [ { "gen": { "height": 55871 } } ], "vout": [ { "amount": 400753208636, "target": { "key": "44af16979d67a647fec19def20cc58a482015de6bb7fb31ba644842b312a5d43" } } ], "extra": [ 1, 78, 9, 49, 118, 54, 26, 231, 80, 162, 200, 36, 46, 141, 139, 199, 139, 55, 23, 20, 46, 13, 58, 116, 47, 105, 87, 52, 250, 7, 95, 235, 174, 2, 17, 0, 0, 0, 3, 255, 88, 174, 148, 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