← previous blocknext block →recent activity
Analyzing
Block #105,582,721
19 transactions · 17 stateful · 2026-09-17 10:34:20 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,582,721 · 19 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
3w011w112w213w314w416w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b42f6a7…f49c
0x34b655…2a6f
8 touches
6 conflicts
0x38b6ee89…0956
0x34b655…2a6f
8 touches
6 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
8 touches
6 conflicts
0xc10b903d…2f54
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2d3930d3…c9b8
0x34b655…2a6f
6 touches
3 conflicts
0x2a58d502…385c
0x34b655…2a6f
4 touches
1 conflict
0xb409e204…89ac
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 0x7b42f6a7e5…ebf49c
Audit this contract →
← previous block·next block →recent activity