← previous blocknext block →recent activity
Analyzing
Block #106,372,960
13 transactions · 11 stateful · 2026-09-20 04:54:06 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,372,960 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0203a60f…d0bd
0x34b655…2a6f
4 touches
1 conflict
0x12e77486…ec2b
0x34b655…2a6f
4 touches
1 conflict
0x1fb8364c…c10d
0x34b655…2a6f
4 touches
1 conflict
0x4a45b318…9716
0x34b655…2a6f
4 touches
1 conflict
0x6b68679f…a232
0x34b655…2a6f
4 touches
1 conflict
0x6d5d1fb5…86a7
0x34b655…2a6f
4 touches
1 conflict
0x74cdc294…26a8
0x34b655…2a6f
4 touches
1 conflict
0x9d6a99f9…da64
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
1 conflict on slot 0x0203a60f30…64d0bd
Audit this contract →
← previous block·next block →recent activity