← previous blocknext block →recent activity
Analyzing
Block #106,575,777
13 transactions · 12 stateful · 2026-09-20 21:54:52 UTC
Parallelism
62/100
Blocked
67%
Avg conflicts / tx
1.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,575,777 · 13 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
1w02w13w14w26w28w310w411w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x159cff26…7665
0x34b655…2a6f
6 touches
3 conflicts
0x3b6e959d…158f
0x34b655…2a6f
6 touches
3 conflicts
0xbe49bf6e…af8b
0x34b655…2a6f
6 touches
3 conflicts
0xc8418042…d6eb
0x34b655…2a6f
6 touches
3 conflicts
0x1a36083f…2a53
0x34b655…2a6f
6 touches
3 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
6 touches
3 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
6 touches
3 conflicts
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 0x1b25f26097…52c429
Audit this contract →
← previous block·next block →recent activity