← previous blocknext block →recent activity
Analyzing
Block #106,453,641
26 transactions · 25 stateful · 2026-09-20 11:40:12 UTC
Parallelism
81/100
Blocked
28%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,453,641 · 26 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
2w07w08w114w015w116w121w122w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x990cc6f8…0e7b
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xe32e848a…851e
0x34b655…2a6f
8 touches
6 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
8 touches
6 conflicts
0xe8058ec4…ebac
0x34b655…2a6f
6 touches
3 conflicts
0x9dd0a735…4d04
0x34b655…2a6f
6 touches
3 conflicts
0xa5811d93…8c73
0x34b655…2a6f
6 touches
3 conflicts
0x7462b8f2…6312
0x34b655…2a6f
6 touches
3 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 0x990cc6f828…0f0e7b
Audit this contract →
← previous block·next block →recent activity