Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c30d75ceb75043374866760688fb74b77a9f0dfa0c0551da4fbdc4b34efca59

Tx prefix hash: 420ab205529b0a48290a9cd04e702991c0f1c027b6ce8852345dcd4928cdc6d9
Tx public key: 2ed84eff9744a95666e5896a15cd12ebe1cfa1bbb017f88ac9a92268d936fd49
Timestamp: 1715571139 Timestamp [UCT]: 2024-05-13 03:32:19 Age [y:d:h:m:s]: 00:289:06:31:10
Block: 1020866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206710 RingCT/type: yes/0
Extra: 012ed84eff9744a95666e5896a15cd12ebe1cfa1bbb017f88ac9a92268d936fd4902110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e21ae9d42e86fb96fb4a8d5ea2accf59dfd6ed79aba7aaab2e37ddfaba83f27 0.600000000000 1484979 of 15

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": 1020876, "vin": [ { "gen": { "height": 1020866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e21ae9d42e86fb96fb4a8d5ea2accf59dfd6ed79aba7aaab2e37ddfaba83f27" } } ], "extra": [ 1, 46, 216, 78, 255, 151, 68, 169, 86, 102, 229, 137, 106, 21, 205, 18, 235, 225, 207, 161, 187, 176, 23, 248, 138, 201, 169, 34, 104, 217, 54, 253, 73, 2, 17, 0, 0, 0, 1, 65, 238, 28, 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