← previous blocknext block →recent activity
Analyzing
Block #87,644,069
24 transactions · 21 stateful · 2026-07-14 06:15:07 UTC
Parallelism
75/100
Blocked
24%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,644,069 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w010w116w017w218w320w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x388633a0…86cd
0x34b655…2a6f
6 touches
3 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0x206fb8db…a146
0x34b655…2a6f
6 touches
3 conflicts
0x2a5e2b11…1c2b
0x34b655…2a6f
6 touches
3 conflicts
0x7946d135…0aad
0x34b655…2a6f
4 touches
1 conflict
0x859c92cc…430b
0x34b655…2a6f
4 touches
1 conflict
0x85ac0ab8…a3d8
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity