← previous blocknext block →recent activity
Analyzing
Block #105,843,807
24 transactions · 22 stateful · 2026-09-18 08:29:52 UTC
Parallelism
67/100
Blocked
64%
Avg conflicts / tx
1.54
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,843,807 · 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
1w02w13w25w17w08w09w110w011w113w215w116w217w318w419w520w621w723w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbdfd584…ab2f
0x34b655…2a6f
14 touches
21 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
14 touches
21 conflicts
0x4118bd12…924a
0x34b655…2a6f
12 touches
15 conflicts
0x0efc210e…70ab
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xffee49e7…f31f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
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
21 conflicts on slot 0xbbdfd5840b…91ab2f
Audit this contract →
← previous block·next block →recent activity