← previous blocknext block →recent activity
Analyzing
Block #87,421,694
22 transactions · 17 stateful · 2026-07-13 05:27:16 UTC
Parallelism
68/100
Blocked
59%
Avg conflicts / tx
1.23
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,421,694 · 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
2w03w14w25w36w49w010w112w515w016w117w218w321w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea4b86ec…900f
0x34b655…2a6f
10 touches
10 conflicts
0x16b3a441…13db
0x34b655…2a6f
8 touches
6 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x727fbce7…0c80
0x34b655…2a6f
8 touches
6 conflicts
0xa457c06e…2f06
0x34b655…2a6f
8 touches
6 conflicts
0xace705e8…625e
0x34b655…2a6f
8 touches
6 conflicts
0xbdc75c16…0d48
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0xea4b86ec74…1a900f
Audit this contract →
← previous block·next block →recent activity