← previous blocknext block →recent activity
Analyzing
Block #93,368,501
19 transactions · 18 stateful · 2026-08-05 14:16:28 UTC
Parallelism
74/100
Blocked
61%
Avg conflicts / tx
0.84
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,368,501 · 19 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
1w02w13w24w05w16w28w19w311w212w213w314w417w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f63a266…68c0
0x34b655…2a6f
6 touches
3 conflicts
0xb4987dc2…6605
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x827557c1…a6be
0x34b655…2a6f
4 touches
1 conflict
0xc0b9bd73…7f1c
0x34b655…2a6f
4 touches
1 conflict
0xc4998e49…c79d
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
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 0x7f63a2661a…b468c0
Audit this contract →
← previous block·next block →recent activity