← previous blocknext block →recent activity
Analyzing
Block #93,368,667
20 transactions · 18 stateful · 2026-08-05 14:17:18 UTC
Parallelism
75/100
Blocked
56%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,368,667 · 20 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
1w02w03w04w15w16w17w28w39w210w312w313w417w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x808129fc…f97d
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x91855e…ac7e
4 touches
1 conflict
0x7aae9795…06ed
0x34b655…2a6f
4 touches
1 conflict
0x8ab7101a…33da
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xac8a5059…fd42
0x34b655…2a6f
4 touches
1 conflict
0xded1a8af…e766
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 0x808129fc27…daf97d
Audit this contract →
← previous block·next block →recent activity