← previous blocknext block →recent activity
Analyzing
Block #106,215,156
21 transactions · 20 stateful · 2026-09-19 15:39:54 UTC
Parallelism
81/100
Blocked
60%
Avg conflicts / tx
0.81
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,215,156 · 21 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
1w02w13w24w05w16w110w011w112w214w015w116w117w318w219w320w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc12ec6f1…9467
0x34b655…2a6f
6 touches
3 conflicts
0x94f4eab2…673c
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xb538c6fa…9aec
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
3 conflicts on slot 0xc12ec6f196…719467
Audit this contract →
← previous block·next block →recent activity