← previous blocknext block →recent activity
Analyzing
Block #92,334,303
13 transactions · 12 stateful · 2026-08-01 23:32:15 UTC
Parallelism
62/100
Blocked
42%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,334,303 · 13 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
2w03w16w07w28w111w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x534ef679…ae9d
0x34b655…2a6f
6 touches
3 conflicts
0x083ff337…401b
0x34b655…2a6f
4 touches
1 conflict
0x0e4000ee…afb9
0x34b655…2a6f
4 touches
1 conflict
0x4ff5ffda…05aa
0x34b655…2a6f
4 touches
1 conflict
0x50d44a56…fe50
0x34b655…2a6f
4 touches
1 conflict
0x6b2ba712…0214
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
3 conflicts on slot 0x534ef679c5…43ae9d
Audit this contract →
← previous block·next block →recent activity