← previous blocknext block →recent activity
Analyzing
Block #106,466,228
18 transactions · 17 stateful · 2026-09-20 12:43:32 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.61
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,466,228 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b4cd909…44a1
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x038b9243…553d
0x34b655…2a6f
4 touches
1 conflict
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0x9c2fc330…0091
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
28 conflicts on slot 0x4b4cd909ad…4c44a1
Audit this contract →
← previous block·next block →recent activity