← previous blocknext block →recent activity
Analyzing
Block #87,585,673
15 transactions · 14 stateful · 2026-07-13 23:44:40 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,585,673 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w09w110w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38d36864…2cb0
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x2ef1d89b…196d
0x754704…b603
4 touches
1 conflict
0xf4ca4a80…b15d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0036
0x35a73b…6042
4 touches
1 conflict
0x33a26eb2…2df0
0x5ff137…2789
4 touches
1 conflict
0xaf831072…51d5
0x69a5f9…2fef
4 touches
1 conflict
0xaf831072…51d6
0x69a5f9…2fef
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 0x38d36864ff…6b2cb0
Audit this contract →
← previous block·next block →recent activity