← previous blocknext block →recent activity
Analyzing
Block #91,440,684
22 transactions · 21 stateful · 2026-07-29 20:37:12 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,440,684 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w09w010w112w216w117w218w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xcc2d6cb7…f7c9
0x34b655…2a6f
6 touches
3 conflicts
0x53cccb07…d7f0
0x34b655…2a6f
6 touches
3 conflicts
0x1889bdd1…e092
0x34b655…2a6f
6 touches
3 conflicts
0xa20a130c…5d59
0x34b655…2a6f
4 touches
2 conflicts
0x279ddfdc…78fb
0x34b655…2a6f
4 touches
1 conflict
0x279ddfdc…78fc
0x34b655…2a6f
4 touches
1 conflict
0x6c143362…7154
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity