← previous blocknext block →recent activity
Analyzing
Block #87,262,903
41 transactions · 34 stateful · 2026-07-12 11:45:23 UTC
Parallelism
71/100
Blocked
65%
Avg conflicts / tx
2.49
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #87,262,903 · 41 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w18w010w111w012w113w214w315w016w117w218w319w420w521w622w723w824w925w1029w631w832w933w135w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0x5cebb016…c149
0x34b655…2a6f
10 touches
10 conflicts
0x7ae63663…9d94
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xb9a7e63b…0e67
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: Perpl
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity