Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0413c60eb670963c7965eee209353a37c409a246e236fec0a7ce991df4093f3

Tx prefix hash: fc574f31efc164e0b6a4a29c2f2bea65304626b6779275ae42baf4d526e80079
Tx public key: 0c3728c3507569b98758c99cae457d2bf87f95c2d335c61f815f69291a55e91e
Timestamp: 1607715956 Timestamp [UCT]: 2020-12-11 19:45:56 Age [y:d:h:m:s]: 04:059:11:21:28
Block: 160323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1054305 RingCT/type: yes/0
Extra: 010c3728c3507569b98758c99cae457d2bf87f95c2d335c61f815f69291a55e91e021100000a6d57f0ba47000000000000000000

1 output(s) for total of 180.640055159000 dcy

stealth address amount amount idx
00: f9efb0eb669838c9b99c045f38e48eff08ca1b1c639d6e9d88be8d568c3905e8 180.640055159000 282232 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": 160333, "vin": [ { "gen": { "height": 160323 } } ], "vout": [ { "amount": 180640055159, "target": { "key": "f9efb0eb669838c9b99c045f38e48eff08ca1b1c639d6e9d88be8d568c3905e8" } } ], "extra": [ 1, 12, 55, 40, 195, 80, 117, 105, 185, 135, 88, 201, 156, 174, 69, 125, 43, 248, 127, 149, 194, 211, 53, 198, 31, 129, 95, 105, 41, 26, 85, 233, 30, 2, 17, 0, 0, 10, 109, 87, 240, 186, 71, 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