← previous blocknext block →recent activity
Analyzing
Block #105,608,131
36 transactions · 25 stateful · 2026-09-17 12:42:15 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,608,131 · 36 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
6w07w08w19w111w019w220w226w327w328w429w132w334w435w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x840b9ed3…5a3e
0x34b655…2a6f
8 touches
6 conflicts
0x8f84702c…c5f9
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1c645adf…cd53
0x34b655…2a6f
5 touches
3 conflicts
0x56e0d685…c960
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 0x840b9ed3a2…5b5a3e
Audit this contract →
← previous block·next block →recent activity