← previous blocknext block →recent activity
Analyzing
Block #93,469,819
10 transactions · 8 stateful · 2026-08-05 22:45:51 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,469,819 · 10 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
2w03w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37a
0x34b655…2a6f
4 touches
1 conflict
0x13ae2a4c…2ee0
0x34b655…2a6f
3 touches
1 conflict
0x15516aa5…fc07
0x34b655…2a6f
3 touches
1 conflict
0xd676e291…3ecf
0x34b655…2a6f
2 touches
0 conflicts
0xdf4f5752…f6e6
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 0x4e8c4408ae…50d37b
Audit this contract →
← previous block·next block →recent activity