← previous blocknext block →recent activity
Analyzing
Block #106,772,294
19 transactions · 19 stateful · 2026-09-21 14:24:54 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,772,294 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w37w49w011w312w414w117w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1bbd371…e541
0x34b655…2a6f
12 touches
15 conflicts
0x7fc8f46e…0f75
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc5cd7d62…6b20
0x34b655…2a6f
6 touches
3 conflicts
0x07bc7a81…f78a
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0x39a63435…cdf2
0x34b655…2a6f
4 touches
1 conflict
0x491abe4d…a6a1
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
15 conflicts on slot 0xf1bbd371ee…44e541
Audit this contract →
← previous block·next block →recent activity