← previous blocknext block →recent activity
Analyzing
Block #87,408,438
18 transactions · 17 stateful · 2026-07-13 03:58:36 UTC
Parallelism
61/100
Blocked
41%
Avg conflicts / tx
0.61
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,408,438 · 18 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
2w04w17w08w29w310w114w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26918bca…6c75
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0x1951ee47…540f
0x34b655…2a6f
4 touches
1 conflict
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x310f723b…fafa
0x34b655…2a6f
4 touches
1 conflict
0x34528a3a…a6d6
0x34b655…2a6f
4 touches
1 conflict
0x34731dbd…e467
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
3 conflicts on slot 0x26918bcabc…d36c75
Audit this contract →
← previous block·next block →recent activity