← previous blocknext block →recent activity
Analyzing
Block #93,662,968
13 transactions · 12 stateful · 2026-08-06 14:56:50 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,662,968 · 13 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
1w02w18w010w111w212w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98212952…9ba6
0x34b655…2a6f
4 touches
1 conflict
0x9ba6ae4a…90cb
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x923c57f1…7810
0x34b655…2a6f
4 touches
1 conflict
0x74852f13…d725
0x065c9d…c394
2 touches
0 conflicts
0xb9e30fde…f837
0x065c9d…c394
2 touches
0 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
1 conflict on slot 0x982129521c…f19ba6
Audit this contract →
← previous block·next block →recent activity