← previous blocknext block →recent activity
Analyzing
Block #92,482,294
17 transactions · 15 stateful · 2026-08-02 11:56:32 UTC
Parallelism
76/100
Blocked
27%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,482,294 · 17 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
1w03w14w06w07w19w010w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2fa00b0…457a
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
0x16f2b4e1…e98b
0x34b655…2a6f
4 touches
1 conflict
0x49c97fd3…6e31
0x34b655…2a6f
4 touches
1 conflict
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0x68a2902c…b23f
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
6 conflicts on slot 0xe2fa00b000…a1457a
Audit this contract →
← previous block·next block →recent activity