← previous blocknext block →recent activity

Analyzing

Block #83,669,552

18 transactions · 17 stateful · 2026-06-25 20:10:18 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

0.83

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #83,669,552  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x13a54fa2…5ae3

0x2a68ba…90c5

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x00000000…0002

0xaa7ee7…f0e4

4 touches
1 conflict

0x11b69a7e…334e

0xee8c0e…1242

4 touches
1 conflict

0x729c91b8…9539

0x188d58…ea8e

4 touches
1 conflict

0xe99d8e68…a16e

0x34b655…2a6f

4 touches
1 conflict

0x729c91b8…9537

0x188d58…ea8e

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: Kuru Exchange: MarginAccount

10 conflicts on slot 0x13a54fa2d3…a35ae3

← previous block·next block →recent activity