← previous blocknext block →recent activity
Analyzing
Block #93,235,639
21 transactions · 21 stateful · 2026-08-05 03:08:28 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,235,639 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w09w111w012w114w117w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16f8e14a…f6e4
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x120847e2…98c2
0x34b655…2a6f
4 touches
1 conflict
0x3dae5ee1…721b
0x34b655…2a6f
4 touches
1 conflict
0x57be321f…fecc
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x82dd2252…e1ce
0x34b655…2a6f
4 touches
1 conflict
0x931bd7a5…b6b9
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 0x16f8e14aad…3ff6e4
Audit this contract →
← previous block·next block →recent activity