← previous blocknext block →recent activity
Analyzing
Block #100,917,807
21 transactions · 21 stateful · 2026-09-01 02:02:45 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,917,807 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w09w110w212w313w315w416w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x099d45d9…cf7f
0x34b655…2a6f
8 touches
6 conflicts
0x55192654…91fe
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x5ae8af42…5824
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x731d7308…fd26
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
6 conflicts on slot 0x099d45d933…b4cf7f
Audit this contract →
← previous block·next block →recent activity