← previous blocknext block →recent activity
Analyzing
Block #87,584,377
25 transactions · 20 stateful · 2026-07-13 23:36:01 UTC
Parallelism
72/100
Blocked
35%
Avg conflicts / tx
0.48
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,584,377 · 25 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
2w03w17w08w112w219w320w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xeea6de0f…51bc
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…0001
0xc1ff9f…b0fc
4 touches
1 conflict
0x1191dbf7…8e85
0x34b655…2a6f
4 touches
1 conflict
0x3a6290da…e683
0x34b655…2a6f
4 touches
1 conflict
0xc9ba1c61…1c8e
0x34b655…2a6f
4 touches
1 conflict
0xdd7aabe0…0f0d
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity