← previous blocknext block →recent activity
Analyzing
Block #93,472,683
26 transactions · 23 stateful · 2026-08-05 23:00:15 UTC
Parallelism
81/100
Blocked
43%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,472,683 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w09w110w211w212w313w314w417w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94bb14fe…8f47
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x890a1db9…1712
0xa6afd3…d132
8 touches
6 conflicts
0x1119ab9e…b631
0x34b655…2a6f
8 touches
6 conflicts
0xa1ff0729…0146
0xa6afd3…d132
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x91855e…ac7e
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 0x94bb14fe40…668f47
Audit this contract →
← previous block·next block →recent activity