← previous blocknext block →recent activity
Analyzing
Block #106,548,280
21 transactions · 21 stateful · 2026-09-20 19:36:29 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,548,280 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w313w017w118w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1032f16c…a9b1
0x34b655…2a6f
8 touches
6 conflicts
0x1a4b4833…cf01
0x34b655…2a6f
8 touches
6 conflicts
0x21e79ad8…c5db
0x34b655…2a6f
8 touches
6 conflicts
0x2f50c84a…3640
0x34b655…2a6f
8 touches
6 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
8 touches
6 conflicts
0x7c2b0f0e…4933
0x34b655…2a6f
8 touches
6 conflicts
0xa7923b81…93a5
0x34b655…2a6f
8 touches
6 conflicts
0xa7d3cb90…e1d9
0x34b655…2a6f
8 touches
6 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 0x1032f16c0e…4fa9b1
Audit this contract →
← previous block·next block →recent activity