← previous blocknext block →recent activity
Analyzing
Block #83,876,950
19 transactions · 17 stateful · 2026-06-26 19:14:09 UTC
Parallelism
89/100
Blocked
12%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,876,950 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w012w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5ee2a98…54a8
0x34b655…2a6f
4 touches
1 conflict
0xd7e72076…294a
0x34b655…2a6f
4 touches
1 conflict
0x99910689…8959
0x34b655…2a6f
4 touches
1 conflict
0x90a9e3f8…17ab
0x34b655…2a6f
4 touches
1 conflict
0xa0592331…1e7f
0x34b655…2a6f
3 touches
1 conflict
0x31b8af78…3e62
0x34b655…2a6f
2 touches
0 conflicts
0x38ec2c24…ef42
0x34b655…2a6f
2 touches
0 conflicts
0x3b6e959d…158f
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xc5ee2a98c8…f854a8
Audit this contract →
← previous block·next block →recent activity