← previous blocknext block →recent activity
Analyzing
Block #91,210,140
32 transactions · 27 stateful · 2026-07-29 01:15:04 UTC
Parallelism
69/100
Blocked
67%
Avg conflicts / tx
1.53
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,210,140 · 32 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
1w03w14w05w17w08w19w210w311w412w513w614w717w218w324w727w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x5cc0e9c8…3ae6
0x34b655…2a6f
10 touches
10 conflicts
0x89678d1b…463e
0xa6afd3…d132
8 touches
6 conflicts
0xd676e291…3ecf
0x34b655…2a6f
8 touches
6 conflicts
0x439cfb2c…7b9e
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x8b87ece6…3353
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity