← previous blocknext block →recent activity
Analyzing
Block #106,276,176
17 transactions · 17 stateful · 2026-09-19 20:47:03 UTC
Parallelism
76/100
Blocked
24%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,276,176 · 17 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
10w011w112w213w014w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fcbf9b2…a36e
0x34b655…2a6f
4 touches
1 conflict
0x9fda36ae…2055
0x34b655…2a6f
4 touches
1 conflict
0xe098738f…9bbe
0x34b655…2a6f
4 touches
1 conflict
0x028892a4…90ac
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x3195e306…7185
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
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
1 conflict on slot 0x8fcbf9b2e6…d7a36e
Audit this contract →
← previous block·next block →recent activity