← previous blocknext block →recent activity
Analyzing
Block #100,626,311
22 transactions · 16 stateful · 2026-08-31 01:36:03 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,626,311 · 22 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
6w07w18w110w011w213w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1ac7bbd…88ad
0x34b655…2a6f
6 touches
3 conflicts
0xe3d7c1f1…1f50
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xfa75029c…d62c
0x34b655…2a6f
6 touches
3 conflicts
0xcaa5e459…c7eb
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
3 conflicts on slot 0xe1ac7bbd43…3e88ad
Audit this contract →
← previous block·next block →recent activity