← previous blocknext block →recent activity
Analyzing
Block #105,920,591
21 transactions · 19 stateful · 2026-09-18 14:57:13 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,920,591 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w16w07w28w19w214w115w216w318w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4089d428…b018
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xa987699f…eabe
0x34ae4d…3fc5
4 touches
1 conflict
0xad3ef711…4f2b
0x34ae4d…3fc5
4 touches
1 conflict
0x5e6b7f61…2ec0
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
3 conflicts on slot 0x4089d42830…afb018
Audit this contract →
← previous block·next block →recent activity