← previous blocknext block →recent activity
Analyzing
Block #93,231,158
10 transactions · 8 stateful · 2026-08-05 02:45:56 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,231,158 · 10 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
1w02w13w14w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x628359b1…7263
0x34b655…2a6f
4 touches
1 conflict
0x6a2521fa…2320
0x34b655…2a6f
4 touches
1 conflict
0x6f8644f7…10fa
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd1fe28c2…d1a9
0x34b655…2a6f
4 touches
1 conflict
0xf17c63a1…a36b
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
1 conflict on slot 0x628359b1c9…1a7263
Audit this contract →
← previous block·next block →recent activity