← previous blocknext block →recent activity
Analyzing
Block #106,454,120
12 transactions · 11 stateful · 2026-09-20 11:42:36 UTC
Parallelism
58/100
Blocked
36%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,454,120 · 12 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
2w03w14w25w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21e79ad8…c5db
0x34b655…2a6f
10 touches
10 conflicts
0x2f50c84a…3640
0x34b655…2a6f
10 touches
10 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
10 touches
10 conflicts
0x5b7fec07…7153
0x34b655…2a6f
10 touches
10 conflicts
0x75f36d60…8556
0x34b655…2a6f
10 touches
10 conflicts
0x844fc686…2d23
0x34b655…2a6f
10 touches
10 conflicts
0x8b7e5c4e…5fae
0x34b655…2a6f
10 touches
10 conflicts
0xbd3735d7…c973
0x34b655…2a6f
10 touches
10 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
10 conflicts on slot 0x21e79ad8cb…30c5db
Audit this contract →
← previous block·next block →recent activity