← previous blocknext block →recent activity
Analyzing
Block #92,961,435
13 transactions · 13 stateful · 2026-08-04 04:08:02 UTC
Parallelism
39/100
Blocked
54%
Avg conflicts / tx
2.15
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,961,435 · 13 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w28w39w410w511w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
10 touches
10 conflicts
0x9927f045…9256
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0x00966e54…7d1d
0x34b655…2a6f
6 touches
3 conflicts
0x15c22181…1354
0x34b655…2a6f
6 touches
3 conflicts
0x6fbc2e5a…e69c
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity