← previous blocknext block →recent activity
Analyzing
Block #93,537,891
15 transactions · 13 stateful · 2026-08-06 04:28:03 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,537,891 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w17w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x424d48b2…e6ae
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x17dd6839…0f1a
0x34b655…2a6f
4 touches
1 conflict
0x27e18872…9e65
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37a
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x5a19ef35…dc70
0x34b655…2a6f
4 touches
1 conflict
0x5b30a6e6…b249
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 0x424d48b260…92e6ae
Audit this contract →
← previous block·next block →recent activity