← previous blocknext block →recent activity
Analyzing
Block #105,880,951
16 transactions · 16 stateful · 2026-09-18 11:36:50 UTC
Parallelism
50/100
Blocked
56%
Avg conflicts / tx
1.63
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,880,951 · 16 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
1w04w05w17w08w29w310w411w512w613w714w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81e66659…a874
0x34b655…2a6f
8 touches
6 conflicts
0x1c7a21bc…03ea
0x34b655…2a6f
8 touches
6 conflicts
0x297de2d5…7396
0x34b655…2a6f
8 touches
6 conflicts
0x9c2fc330…0091
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x4988d313…da91
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x4be9812b…48a9
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0x81e666590c…8fa874
Audit this contract →
← previous block·next block →recent activity