← previous blocknext block →recent activity
Analyzing
Block #93,436,835
70 transactions · 68 stateful · 2026-08-05 20:00:02 UTC
Parallelism
96/100
Blocked
4%
Avg conflicts / tx
0.07
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,436,835 · 70 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
1w05w063w164w167w068w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0x9af5f9b9…06e8
0x34b655…2a6f
4 touches
1 conflict
0x92d610a6…9a40
0x2a68ba…90c5
2 touches
0 conflicts
0x997ccc40…4dfd
0x3bd359…433a
2 touches
0 conflicts
0xe2745681…ff50
0x3bd359…433a
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
3 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity