← previous blocknext block →recent activity
Analyzing
Block #93,371,366
24 transactions · 24 stateful · 2026-08-05 14:30:53 UTC
Parallelism
75/100
Blocked
58%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,371,366 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w16w27w38w49w213w314w115w519w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x84b98a86…5c11
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xfd42a6b9…4c81
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x3d158563…8713
0x34b655…2a6f
6 touches
3 conflicts
0xfecb18c0…01ed
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x84b98a86ac…c45c11
Audit this contract →
← previous block·next block →recent activity