Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f82b1c44b0ee5c2688181b7a99c383fddbb00396e602d8381cd24a7dd7bab16

Tx prefix hash: 344abb19927d30b702d31c07895a93b1a4b3480a6a8de921c63aa65d5d6edeef
Tx public key: 86c07978dc88f15466c7684eebea61a104533e3adcf23ea1f444701f9444be30
Timestamp: 1578953094 Timestamp [UCT]: 2020-01-13 22:04:54 Age [y:d:h:m:s]: 04:321:05:11:41
Block: 44991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119000 RingCT/type: yes/0
Extra: 0186c07978dc88f15466c7684eebea61a104533e3adcf23ea1f444701f9444be3002110000000b4943cd9f000000000000000000

1 output(s) for total of 435.438655825000 dcy

stealth address amount amount idx
00: ec4182dc3bda79d8b9d65a874b1a87022551b16cf34291367e6c8249ea03c054 435.438655825000 82049 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": 45001, "vin": [ { "gen": { "height": 44991 } } ], "vout": [ { "amount": 435438655825, "target": { "key": "ec4182dc3bda79d8b9d65a874b1a87022551b16cf34291367e6c8249ea03c054" } } ], "extra": [ 1, 134, 192, 121, 120, 220, 136, 241, 84, 102, 199, 104, 78, 235, 234, 97, 161, 4, 83, 62, 58, 220, 242, 62, 161, 244, 68, 112, 31, 148, 68, 190, 48, 2, 17, 0, 0, 0, 11, 73, 67, 205, 159, 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