← previous blocknext block →recent activity
Analyzing
Block #93,064,028
9 transactions · 8 stateful · 2026-08-04 12:44:19 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,064,028 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23eeba48…cc51
0x34b655…2a6f
4 touches
1 conflict
0x4102cb2a…3b17
0x34b655…2a6f
4 touches
1 conflict
0xc308125c…f0d6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd0aebe26…167d
0x34b655…2a6f
4 touches
1 conflict
0x0f97bf50…c21f
0x34b655…2a6f
2 touches
0 conflicts
0x11cef08f…e949
0x34b655…2a6f
2 touches
0 conflicts
0x13a10171…0f36
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 0x23eeba48a8…ddcc51
Audit this contract →
← previous block·next block →recent activity