← previous blocknext block →recent activity
Analyzing
Block #106,187,282
30 transactions · 26 stateful · 2026-09-19 13:19:35 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,187,282 · 30 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
1w02w13w14w25w06w117w018w119w224w225w326w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c9f9f29…3e58
0x34b655…2a6f
8 touches
6 conflicts
0x82fd45e4…0935
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x1cdfe548…d3aa
0x34b655…2a6f
8 touches
6 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xba1edffb…323e
0x34b655…2a6f
8 touches
6 conflicts
0x6771eae2…7014
0x34b655…2a6f
8 touches
6 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 0x9c9f9f296d…453e58
Audit this contract →
← previous block·next block →recent activity