← previous blocknext block →recent activity
Analyzing
Block #91,432,965
30 transactions · 27 stateful · 2026-07-29 19:58:22 UTC
Parallelism
67/100
Blocked
63%
Avg conflicts / tx
1.67
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,432,965 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w49w510w011w112w213w314w416w219w122w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xda2ee2e7…968a
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x92115abd…ad76
0x34b655…2a6f
6 touches
3 conflicts
0x297d32d2…89f1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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: 0x48cba278…e2b48b
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity