← previous blocknext block →recent activity
Analyzing
Block #93,438,889
13 transactions · 13 stateful · 2026-08-05 20:10:22 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,438,889 · 13 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
2w03w14w26w310w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c7159f3…4391
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x29265bf3…16ba
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x69a45f39…39aa
0x34b655…2a6f
6 touches
3 conflicts
0xbcab7dbe…2825
0x34b655…2a6f
6 touches
3 conflicts
0x9af5f9b9…06e8
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
6 conflicts on slot 0x0c7159f3e7…eb4391
Audit this contract →
← previous block·next block →recent activity