← previous blocknext block →recent activity
Analyzing
Block #92,068,559
15 transactions · 15 stateful · 2026-08-01 01:15:45 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,068,559 · 15 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
2w05w16w27w28w312w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68ca40a2…bc7c
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x033cf007…136d
0x34b655…2a6f
6 touches
3 conflicts
0xf51ec09c…b4a9
0x34b655…2a6f
6 touches
3 conflicts
0x62b26c37…87d6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xb6ad868e…704c
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 0x68ca40a29b…6fbc7c
Audit this contract →
← previous block·next block →recent activity