← previous blocknext block →recent activity
Analyzing
Block #91,276,803
25 transactions · 20 stateful · 2026-07-29 06:51:15 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,276,803 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w115w116w217w320w222w323w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf4f9cac7…fd98
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x5502e1cc…3910
0x34b655…2a6f
4 touches
1 conflict
0x6389e166…e1ba
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x0899947a…48a7
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity