← previous blocknext block →recent activity
Analyzing
Block #83,632,211
17 transactions · 14 stateful · 2026-06-25 16:01:07 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,632,211 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w19w013w114w215w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d4b0baf…1423
0x34b655…2a6f
4 touches
1 conflict
0x369a11e2…566f
0x34b655…2a6f
4 touches
1 conflict
0x6ca8bab1…3957
0x34b655…2a6f
4 touches
1 conflict
0xa26efe71…a8ef
0x34b655…2a6f
4 touches
1 conflict
0xbd68c7c7…40b3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
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
1 conflict on slot 0x1d4b0bafd5…641423
Audit this contract →
← previous block·next block →recent activity