← previous blocknext block →recent activity
Analyzing
Block #105,933,019
25 transactions · 25 stateful · 2026-09-18 15:59:47 UTC
Parallelism
84/100
Blocked
36%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,933,019 · 25 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
1w02w03w04w15w26w011w012w114w116w117w218w323w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9bd1564b…dfe8
0x34b655…2a6f
6 touches
3 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
6 touches
3 conflicts
0xc313b881…fdcb
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xe796f8b7…ad55
0x34b655…2a6f
6 touches
3 conflicts
0x39aafc65…aa29
0x34b655…2a6f
6 touches
3 conflicts
0x4786839b…c29a
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 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
3 conflicts on slot 0x9bd1564b03…afdfe8
Audit this contract →
← previous block·next block →recent activity