← previous blocknext block →recent activity
Analyzing
Block #105,858,912
24 transactions · 24 stateful · 2026-09-18 09:45:55 UTC
Parallelism
67/100
Blocked
54%
Avg conflicts / tx
1.79
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,858,912 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w110w211w112w313w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcfbd5d39…860b
0x34b655…2a6f
16 touches
28 conflicts
0x588380ee…0a5c
0x34b655…2a6f
10 touches
10 conflicts
0xb3aa2022…9e09
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x4abfb389…18f4
0x34b655…2a6f
8 touches
6 conflicts
0xab981df1…2941
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x7bf4ea6c…3cdc
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
28 conflicts on slot 0xcfbd5d392f…e8860b
Audit this contract →
← previous block·next block →recent activity