Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 534f7b1a9ef5d3da3c6101390bf378d08c97edc382de605a682904299157ceba

Tx prefix hash: 644a4589a26e94566093aa46fb7b56562b912fe88deaa1173fc533385491e362
Tx public key: ccceccc833afd3f833b2c10db4004882871ca916150ab7fa6e32333d0d0e6f0b
Timestamp: 1695281964 Timestamp [UCT]: 2023-09-21 07:39:24 Age [y:d:h:m:s]: 01:157:04:21:55
Block: 852827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373375 RingCT/type: yes/0
Extra: 01ccceccc833afd3f833b2c10db4004882871ca916150ab7fa6e32333d0d0e6f0b021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.916706216000 dcy

stealth address amount amount idx
00: 0c5811d89c6e668be6fd2ce3959cc2cb3169b88698828d9c1222e2672ff497df 0.916706216000 1306687 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": 852837, "vin": [ { "gen": { "height": 852827 } } ], "vout": [ { "amount": 916706216, "target": { "key": "0c5811d89c6e668be6fd2ce3959cc2cb3169b88698828d9c1222e2672ff497df" } } ], "extra": [ 1, 204, 206, 204, 200, 51, 175, 211, 248, 51, 178, 193, 13, 180, 0, 72, 130, 135, 28, 169, 22, 21, 10, 183, 250, 110, 50, 51, 61, 13, 14, 111, 11, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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