← previous blocknext block →recent activity
Analyzing
Block #93,360,734
23 transactions · 22 stateful · 2026-08-05 13:37:25 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,360,734 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w38w49w510w611w312w415w520w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38bdc5d3…a632
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xd30f9e74…d404
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7d16a9bc…25db
0x34b655…2a6f
4 touches
1 conflict
0xa1db0634…3c6c
0x34b655…2a6f
4 touches
1 conflict
0xab5ba139…ea6f
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
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
10 conflicts on slot 0x38bdc5d3e1…01a632
Audit this contract →
← previous block·next block →recent activity