← previous blocknext block →recent activity
Analyzing
Block #87,333,299
15 transactions · 15 stateful · 2026-07-12 19:36:06 UTC
Parallelism
60/100
Blocked
47%
Avg conflicts / tx
1.07
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,333,299 · 15 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
2w03w14w25w16w27w38w413w014w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa013ecc1…7c8f
0x34b655…2a6f
8 touches
6 conflicts
0xe85e763f…3b25
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1a8
0xb1dbf0…c0d3
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0xb8c255af…052c
0x34b655…2a6f
4 touches
1 conflict
0xdb3937e8…23cb
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 0xa013ecc17b…017c8f
Audit this contract →
← previous block·next block →recent activity