← previous blocknext block →recent activity
Analyzing
Block #106,099,676
17 transactions · 14 stateful · 2026-09-19 05:58:41 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,099,676 · 17 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
1w03w05w112w013w014w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b4fc04c…7352
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x214f87c0…9db8
0x34b655…2a6f
4 touches
1 conflict
0x04d962b7…1cc0
0x34b655…2a6f
2 touches
0 conflicts
0x0e216931…58c3
0x34b655…2a6f
2 touches
0 conflicts
0x32be917c…438b
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 0x1b4fc04ce3…497352
Audit this contract →
← previous block·next block →recent activity