← previous blocknext block →recent activity
Analyzing
Block #105,845,632
23 transactions · 18 stateful · 2026-09-18 08:39:05 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,845,632 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w06w17w08w19w210w113w314w415w520w321w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xacb328a9…1e56
0xd32edf…ff58
5 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x70d81211…f49f
0x34b655…2a6f
4 touches
1 conflict
0xa43a396b…ed39
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf66a6da0…4edb
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity