← previous blocknext block →recent activity
Analyzing
Block #83,845,985
20 transactions · 16 stateful · 2026-06-26 15:47:33 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,845,985 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w18w29w314w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0x7c5260f4…bd96
0xa6afd3…d132
6 touches
3 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
6 touches
3 conflicts
0xb3975d93…b4a2
0x34b655…2a6f
6 touches
3 conflicts
0x882df98d…78a9
0x34b655…2a6f
6 touches
3 conflicts
0x8726ff39…3be8
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity