← previous blocknext block →recent activity
Analyzing
Block #92,113,067
20 transactions · 19 stateful · 2026-08-01 04:59:34 UTC
Parallelism
55/100
Blocked
47%
Avg conflicts / tx
1.85
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #92,113,067 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w210w311w412w513w615w716w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xaa3c398a…05d0
0x34b655…2a6f
16 touches
28 conflicts
0xff196840…a453
0x34b655…2a6f
14 touches
21 conflicts
0x4abfb389…18f4
0x34b655…2a6f
8 touches
6 conflicts
0x5d1ac445…5233
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xd895ee0b…d301
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
28 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity