← previous blocknext block →recent activity
Analyzing
Block #87,059,227
14 transactions · 12 stateful · 2026-07-11 13:03:23 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,059,227 · 14 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
1w02w14w05w16w07w010w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf47f6edc…f5d7
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x8a35acfb…d1a8
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1ac
0xb1dbf0…c0d3
4 touches
1 conflict
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0x43ffd8bd…0d0c
0x34b655…2a6f
4 touches
1 conflict
0xba639250…76be
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
1 conflict on slot 0xf47f6edc01…e6f5d7
Audit this contract →
← previous block·next block →recent activity