← previous blocknext block →recent activity
Analyzing
Block #91,248,234
34 transactions · 33 stateful · 2026-07-29 04:26:45 UTC
Parallelism
62/100
Blocked
64%
Avg conflicts / tx
1.85
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #91,248,234 · 34 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w49w510w614w1018w120w122w223w327w1128w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x6e6b8ec7…2197
0x34b655…2a6f
10 touches
10 conflicts
0xa20a130c…5d59
0x34b655…2a6f
10 touches
10 conflicts
0x539ac47f…eb6f
0x34b655…2a6f
8 touches
6 conflicts
0xdedb1b9a…b33b
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity