Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2593266ffc8af7ff4383411ff919828d8265dfa0a9669e1e681a2a2ef182f2f

Tx prefix hash: fe08b27f90bb479d4c87cdd92dfd4e1ecc636d84670595b970fa84ffd85cb2f2
Tx public key: 923c44b49fc7cb066abcfec9ee1db793778de3b2c68b8f33a69b10f532451635
Timestamp: 1583541054 Timestamp [UCT]: 2020-03-07 00:30:54 Age [y:d:h:m:s]: 04:296:08:31:58
Block: 78045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106139 RingCT/type: yes/0
Extra: 01923c44b49fc7cb066abcfec9ee1db793778de3b2c68b8f33a69b10f53245163502110000002a4943cd9f000000000000000000

1 output(s) for total of 338.380485959000 dcy

stealth address amount amount idx
00: c4a4d900481f7c830c24cbbf63a535d5b1b54148688c9b6b56ce3f3973aeac36 338.380485959000 143302 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": 78055, "vin": [ { "gen": { "height": 78045 } } ], "vout": [ { "amount": 338380485959, "target": { "key": "c4a4d900481f7c830c24cbbf63a535d5b1b54148688c9b6b56ce3f3973aeac36" } } ], "extra": [ 1, 146, 60, 68, 180, 159, 199, 203, 6, 106, 188, 254, 201, 238, 29, 183, 147, 119, 141, 227, 178, 198, 139, 143, 51, 166, 155, 16, 245, 50, 69, 22, 53, 2, 17, 0, 0, 0, 42, 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