← previous blocknext block →recent activity
Analyzing
Block #105,550,042
17 transactions · 16 stateful · 2026-09-17 07:49:53 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.35
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,550,042 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w210w312w413w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4073f47e…39e6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xc948dbdc…199a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf496f80c…d5c8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x27b6010e…e4aa
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
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
1 conflict on slot 0x4073f47ec9…f139e6
Audit this contract →
← previous block·next block →recent activity