← previous blocknext block →recent activity
Analyzing
Block #106,423,732
10 transactions · 10 stateful · 2026-09-20 09:09:36 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,423,732 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w18w09w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99d66bcb…0fcb
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x08de772c…8e84
0x2a68ba…90c5
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x018b3072…c22a
0x34b655…2a6f
2 touches
0 conflicts
0x02fa927d…6468
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x99d66bcbbb…f30fcb
Audit this contract →
← previous block·next block →recent activity