← previous blocknext block →recent activity
Analyzing
Block #83,640,575
16 transactions · 14 stateful · 2026-06-25 16:57:00 UTC
Parallelism
50/100
Blocked
57%
Avg conflicts / tx
1.31
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,640,575 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w29w310w411w513w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e86dd1e…dc3e
0x34b655…2a6f
10 touches
10 conflicts
0x1222e42d…7dc8
0x34b655…2a6f
9 touches
10 conflicts
0x83c63e7d…28c6
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x7e6c970a…65af
0x34b655…2a6f
6 touches
3 conflicts
0xb1c67a7d…b9b1
0x34b655…2a6f
6 touches
3 conflicts
0xbb3504d4…b05f
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x2e86dd1e84…99dc3e
Audit this contract →
← previous block·next block →recent activity