← previous blocknext block →recent activity
Analyzing
Block #100,248,691
7 transactions · 6 stateful · 2026-08-29 17:53:09 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,248,691 · 7 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
2w04w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x7ac265cd…0253
0x34b655…2a6f
4 touches
1 conflict
0x1fb8364c…c10d
0x34b655…2a6f
4 touches
1 conflict
0x23e6fc0f…f11d
0x34b655…2a6f
2 touches
0 conflicts
0x290abc80…f605
0x34b655…2a6f
2 touches
0 conflicts
0x290abc80…f606
0x34b655…2a6f
2 touches
0 conflicts
0x29b83fb3…a261
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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity