← previous blocknext block →recent activity
Analyzing
Block #100,870,130
21 transactions · 21 stateful · 2026-08-31 22:02:57 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.67
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,870,130 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w212w313w414w517w619w220w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c455afd…ce06
0x34b655…2a6f
6 touches
3 conflicts
0xf4b2a427…0234
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x534b48d3…7851
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x9c1b5056…8e3b
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 0x5c455afdfc…27ce06
Audit this contract →
← previous block·next block →recent activity