← previous blocknext block →recent activity
Analyzing
Block #92,534,118
19 transactions · 19 stateful · 2026-08-02 16:17:10 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,534,118 · 19 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
2w03w14w25w26w37w48w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xff196840…a453
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x88b81e23…29b3
0x34b655…2a6f
6 touches
3 conflicts
0x839be85f…a40b
0x34b655…2a6f
6 touches
3 conflicts
0x45f48a5c…0a93
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity