← previous blocknext block →recent activity
Analyzing
Block #106,945,069
23 transactions · 22 stateful · 2026-09-22 04:54:35 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,945,069 · 23 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
1w04w16w210w311w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x858e40c0…7e30
0x34b655…2a6f
4 touches
1 conflict
0x6cad301f…15b7
0x34b655…2a6f
4 touches
1 conflict
0x6f9b02f3…07d5
0x34b655…2a6f
4 touches
1 conflict
0x232b0b19…d946
0x34b655…2a6f
2 touches
0 conflicts
0x2a577113…a1bd
0x34b655…2a6f
2 touches
0 conflicts
0x38de667a…9370
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity