← previous blocknext block →recent activity
Analyzing
Block #87,696,298
13 transactions · 13 stateful · 2026-07-14 12:04:06 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,696,298 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w09w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf386bff1…b350
0x34b655…2a6f
4 touches
1 conflict
0x17fbe072…2ea6
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x9efebfcf…9e65
0x34b655…2a6f
4 touches
1 conflict
0xa5060afa…ec77
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0x915c095e…c1e5
0x2b46c0…1669
2 touches
0 conflicts
0xcfe06a18…b5b5
0x2b46c0…1669
2 touches
0 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
1 conflict on slot 0xf386bff13e…f6b350
Audit this contract →
← previous block·next block →recent activity