← previous blocknext block →recent activity
Analyzing
Block #106,916,749
22 transactions · 21 stateful · 2026-09-22 02:32:02 UTC
Parallelism
73/100
Blocked
52%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,916,749 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w19w212w313w015w417w118w219w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fc8f46e…0f75
0x34b655…2a6f
10 touches
10 conflicts
0x3d2785ea…dd64
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x125f12…a50b
4 touches
1 conflict
0x2130a548…c1de
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
10 conflicts on slot 0x7fc8f46ef5…dd0f75
Audit this contract →
← previous block·next block →recent activity