← previous blocknext block →recent activity
Analyzing
Block #106,474,538
19 transactions · 17 stateful · 2026-09-20 13:25:21 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,474,538 · 19 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
1w04w05w17w29w010w114w117w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x844fc686…2d23
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0xfd4e632c…e14c
0x34b655…2a6f
6 touches
3 conflicts
0x21e79ad8…c5db
0x34b655…2a6f
4 touches
1 conflict
0x2f50c84a…3640
0x34b655…2a6f
4 touches
1 conflict
0x3c70ac8d…eaf2
0x34b655…2a6f
4 touches
1 conflict
0x5ad5e6de…e7ad
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
3 conflicts on slot 0x844fc686bd…642d23
Audit this contract →
← previous block·next block →recent activity