← previous blocknext block →recent activity
Analyzing
Block #83,634,014
35 transactions · 25 stateful · 2026-06-25 16:13:10 UTC
Parallelism
80/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,634,014 · 35 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w27w09w115w016w117w018w119w220w321w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
6 touches
3 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
6 touches
3 conflicts
0xe2e45419…f17b
0x34b655…2a6f
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
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: Perpl
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity