← previous blocknext block →recent activity
Analyzing
Block #105,919,429
33 transactions · 25 stateful · 2026-09-18 14:51:21 UTC
Parallelism
88/100
Blocked
32%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,919,429 · 33 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w06w011w115w117w120w121w222w326w027w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xe0493116…7035
0x34b655…2a6f
6 touches
3 conflicts
0xecca4dd0…4770
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x4ee0b65a…6d40
0x34b655…2a6f
6 touches
3 conflicts
0xd79c9727…1233
0x34b655…2a6f
6 touches
3 conflicts
0xdbb571e4…6829
0x34b655…2a6f
4 touches
1 conflict
0x4d5b0ee6…9d42
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity