← previous blocknext block →recent activity
Analyzing
Block #106,030,868
21 transactions · 16 stateful · 2026-09-19 00:12:25 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,030,868 · 21 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
1w02w07w18w09w110w211w312w418w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x197c6711…a146
0x34b655…2a6f
8 touches
6 conflicts
0x65903ef9…2567
0x34b655…2a6f
8 touches
6 conflicts
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0x085df2c1…305a
0x34b655…2a6f
6 touches
3 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
6 touches
3 conflicts
0x304ce1c3…a4db
0x34b655…2a6f
6 touches
3 conflicts
0x3f152ba8…cea6
0x34b655…2a6f
6 touches
3 conflicts
0x45885570…ed97
0x34b655…2a6f
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
6 conflicts on slot 0x197c671148…1fa146
Audit this contract →
← previous block·next block →recent activity