← previous blocknext block →recent activity
Analyzing
Block #100,786,667
10 transactions · 9 stateful · 2026-08-31 15:02:50 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,786,667 · 10 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
2w05w16w07w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafb22303…6db3
0x34b655…2a6f
4 touches
1 conflict
0x09bd1e16…1992
0x34b655…2a6f
4 touches
1 conflict
0x97e4c862…4419
0x34b655…2a6f
4 touches
1 conflict
0x3ab69617…1e2e
0x34b655…2a6f
4 touches
1 conflict
0x78eb0de5…1db2
0x01bff4…1071
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
2 touches
0 conflicts
0x155e52ca…fac7
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 0xafb22303eb…7c6db3
Audit this contract →
← previous block·next block →recent activity