← previous blocknext block →recent activity
Analyzing
Block #106,109,992
24 transactions · 24 stateful · 2026-09-19 06:50:36 UTC
Parallelism
63/100
Blocked
54%
Avg conflicts / tx
1.46
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,109,992 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w211w312w414w515w616w717w823w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16867f4f…0bb3
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x80398c66…f3cc
0x34b655…2a6f
8 touches
6 conflicts
0xa4d37162…967c
0x34b655…2a6f
8 touches
6 conflicts
0xab981df1…2941
0x34b655…2a6f
8 touches
6 conflicts
0xba1edffb…323e
0x34b655…2a6f
8 touches
6 conflicts
0xbc417c5e…4f97
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 0x16867f4f3f…240bb3
Audit this contract →
← previous block·next block →recent activity