Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3077ba83d06c90f70b75c975f871fb11650826b2793c609e7eed6504638c1dfc

Tx prefix hash: 9a0859b37845d04ff525a84fde847f572f24a56c027199b7f7f7dc05a94a21a9
Tx public key: 209a4371a317bb9ac70fe4472fa6ecee2f4b05eacba9913955091b74c698356c
Timestamp: 1581475976 Timestamp [UCT]: 2020-02-12 02:52:56 Age [y:d:h:m:s]: 04:356:05:53:40
Block: 63242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1146427 RingCT/type: yes/0
Extra: 01209a4371a317bb9ac70fe4472fa6ecee2f4b05eacba9913955091b74c698356c02110000000e724f989b000000000000000000

1 output(s) for total of 378.838243726000 dcy

stealth address amount amount idx
00: e6a2ce6f633856dee6b8926b2a13f4ccf576ea37d34725a3365e03570f34d8f8 378.838243726000 116579 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": 63252, "vin": [ { "gen": { "height": 63242 } } ], "vout": [ { "amount": 378838243726, "target": { "key": "e6a2ce6f633856dee6b8926b2a13f4ccf576ea37d34725a3365e03570f34d8f8" } } ], "extra": [ 1, 32, 154, 67, 113, 163, 23, 187, 154, 199, 15, 228, 71, 47, 166, 236, 238, 47, 75, 5, 234, 203, 169, 145, 57, 85, 9, 27, 116, 198, 152, 53, 108, 2, 17, 0, 0, 0, 14, 114, 79, 152, 155, 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