← previous blocknext block →recent activity
Analyzing
Block #106,952,933
32 transactions · 28 stateful · 2026-09-22 05:34:10 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,952,933 · 32 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
1w02w03w16w09w110w011w212w116w020w321w122w223w324w125w430w031w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8d5fc820…1750
0x34b655…2a6f
6 touches
3 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x6999d652…4d6a
0x065c9d…c394
5 touches
3 conflicts
0x65903ef9…2567
0x34b655…2a6f
4 touches
1 conflict
0x7af00ec1…42ae
0x34b655…2a6f
4 touches
1 conflict
0x9375a764…dca1
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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity