← previous blocknext block →recent activity
Analyzing
Block #106,377,184
33 transactions · 31 stateful · 2026-09-20 05:15:21 UTC
Parallelism
82/100
Blocked
52%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,377,184 · 33 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w38w49w518w222w323w125w226w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c840894…764a
0x34b655…2a6f
12 touches
15 conflicts
0x000bde1a…e123
0x34b655…2a6f
8 touches
6 conflicts
0x8ed1e6fc…6701
0x34b655…2a6f
8 touches
6 conflicts
0x298e7eb7…0c5c
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
15 conflicts on slot 0x1c84089465…17764a
Audit this contract →
← previous block·next block →recent activity