← previous blocknext block →recent activity
Analyzing
Block #93,510,777
14 transactions · 13 stateful · 2026-08-06 02:11:46 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,510,777 · 14 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
2w03w15w26w311w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ab787fc…6a13
0x34b655…2a6f
4 touches
1 conflict
0xa13e2069…6171
0x34b655…2a6f
4 touches
1 conflict
0xb5681617…e980
0x34b655…2a6f
4 touches
1 conflict
0xbc25e327…a1ca
0x34b655…2a6f
4 touches
1 conflict
0xc6b9bb4b…145a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd3d2b624…594f
0x34b655…2a6f
4 touches
1 conflict
0x63bed776…8d4a
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
1 conflict on slot 0x3ab787fc63…e46a13
Audit this contract →
← previous block·next block →recent activity