← previous blocknext block →recent activity
Analyzing
Block #106,545,391
21 transactions · 18 stateful · 2026-09-20 19:21:57 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,545,391 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w210w311w412w516w019w120w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x21e79ad8…c5db
0x34b655…2a6f
4 touches
1 conflict
0x2f50c84a…3640
0x34b655…2a6f
4 touches
1 conflict
0x3c9b10c1…d791
0x34b655…2a6f
4 touches
1 conflict
0x4ae38164…15f0
0x34b655…2a6f
4 touches
1 conflict
0x5ad5e6de…e7ad
0x34b655…2a6f
4 touches
1 conflict
0x656c2ba5…d35b
0x34b655…2a6f
4 touches
1 conflict
0x784f870c…0bfb
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
15 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity