← previous blocknext block →recent activity
Analyzing
Block #93,291,341
21 transactions · 20 stateful · 2026-08-05 07:48:32 UTC
Parallelism
76/100
Blocked
35%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,291,341 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w07w08w010w111w212w314w415w117w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cf222e0…54e5
0x34b655…2a6f
8 touches
6 conflicts
0x746bcce3…d0ce
0x34b655…2a6f
6 touches
3 conflicts
0x94de4d05…ad01
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7938c6fd…1cd1
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2db
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
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
6 conflicts on slot 0x7cf222e0f5…d354e5
Audit this contract →
← previous block·next block →recent activity