← previous blocknext block →recent activity
Analyzing
Block #92,072,387
18 transactions · 16 stateful · 2026-08-01 01:35:00 UTC
Parallelism
61/100
Blocked
56%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,072,387 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w38w49w511w512w615w516w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x427c9fc4…5cee
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x2bb0d58d…9dcf
0x34b655…2a6f
6 touches
3 conflicts
0xafe6567a…4f0a
0x34b655…2a6f
6 touches
3 conflicts
0x96d1711a…347c
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab0
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
21 conflicts on slot 0x427c9fc46b…895cee
Audit this contract →
← previous block·next block →recent activity