← previous blocknext block →recent activity
Analyzing
Block #106,924,248
27 transactions · 24 stateful · 2026-09-22 03:09:47 UTC
Parallelism
81/100
Blocked
42%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,924,248 · 27 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
1w05w06w18w09w110w211w012w115w216w218w221w222w325w026w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xea2d1275…76c8
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xb2dda82c…e376
0x34b655…2a6f
6 touches
3 conflicts
0xc137f51f…cd2e
0x851145…3f07
4 touches
1 conflict
0x7ffc11ef…28ee
0x065c9d…c394
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity