← previous blocknext block →recent activity
Analyzing
Block #100,131,995
33 transactions · 14 stateful · 2026-08-29 08:04:53 UTC
Parallelism
94/100
Blocked
7%
Avg conflicts / tx
0.03
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,131,995 · 33 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
29w030w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9874e36…beed
0x34b655…2a6f
4 touches
1 conflict
0x0efc210e…70ab
0x34b655…2a6f
4 touches
1 conflict
0x53f7214d…8ec6
0x34b655…2a6f
4 touches
1 conflict
0x5da59c2b…d7b2
0x34b655…2a6f
4 touches
1 conflict
0xea8abd9b…92c8
0x34b655…2a6f
4 touches
1 conflict
0x0476d77b…a514
0x34b655…2a6f
2 touches
0 conflicts
0x0ac16ad4…2493
0x34b655…2a6f
2 touches
0 conflicts
0x1e168c8b…6945
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 0xf9874e3690…90beed
Audit this contract →
← previous block·next block →recent activity