← previous blocknext block →recent activity
Analyzing
Block #106,189,407
33 transactions · 23 stateful · 2026-09-19 13:30:16 UTC
Parallelism
88/100
Blocked
43%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,189,407 · 33 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
3w04w05w17w08w19w011w117w120w121w224w125w229w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9baf24c…c1fe
0x34b655…2a6f
6 touches
3 conflicts
0xfcdb5918…2b49
0x34b655…2a6f
6 touches
3 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0x1b458e47…5ab5
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x8b87ece6…3353
0x34b655…2a6f
4 touches
1 conflict
0x932a9590…0b19
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 0xf9baf24cdf…38c1fe
Audit this contract →
← previous block·next block →recent activity