← previous blocknext block →recent activity
Analyzing
Block #93,241,638
16 transactions · 16 stateful · 2026-08-05 03:38:37 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,241,638 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w08w110w211w312w413w514w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x059bff94…6c87
0x34b655…2a6f
8 touches
6 conflicts
0xf9e23360…8ef7
0x34b655…2a6f
8 touches
6 conflicts
0x31b39922…1e66
0x34b655…2a6f
6 touches
3 conflicts
0x033cf007…136d
0x34b655…2a6f
6 touches
3 conflicts
0x31b39922…1e65
0x34b655…2a6f
6 touches
3 conflicts
0x6719a767…9d62
0x34b655…2a6f
6 touches
3 conflicts
0xb4317885…7775
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x059bff94da…0d6c87
Audit this contract →
← previous block·next block →recent activity