← previous blocknext block →recent activity
Analyzing
Block #100,619,256
25 transactions · 23 stateful · 2026-08-31 01:00:33 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,619,256 · 25 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
1w02w03w16w19w210w212w313w417w322w023w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd7f5b55…4994
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb3037bed…6b7c
0x34b655…2a6f
6 touches
3 conflicts
0x661e648a…2aa7
0x34b655…2a6f
6 touches
3 conflicts
0x279ddfdc…78fc
0x34b655…2a6f
4 touches
1 conflict
0x5e8a4db9…a764
0x34b655…2a6f
4 touches
1 conflict
0x731d7308…fd26
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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 0xfd7f5b557f…f74994
Audit this contract →
← previous block·next block →recent activity