← previous blocknext block →recent activity
Analyzing
Block #106,154,901
11 transactions · 11 stateful · 2026-09-19 10:36:37 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,154,901 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xc37c0d8b…7bb8
0x34b655…2a6f
4 touches
1 conflict
0x0145aa28…106b
0x34b655…2a6f
2 touches
0 conflicts
0x1d63d27d…dbe7
0x34b655…2a6f
2 touches
0 conflicts
0x2d4b76b6…d903
0x34b655…2a6f
2 touches
0 conflicts
0x46714a72…19bc
0x34b655…2a6f
2 touches
0 conflicts
0x4c9e5bd1…ef8c
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
1 conflict on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity