← previous blocknext block →recent activity
Analyzing
Block #87,643,661
16 transactions · 14 stateful · 2026-07-14 06:12:24 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,643,661 · 16 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
6w08w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72083f0d…082a
0x34b655…2a6f
4 touches
1 conflict
0x25db999f…f707
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x4814529d…5f07
0x34b655…2a6f
4 touches
1 conflict
0x4f4a7ac3…021c
0x34b655…2a6f
4 touches
1 conflict
0x19795ad6…4a16
0x34b655…2a6f
2 touches
0 conflicts
0x2bb0d58d…9dcf
0x34b655…2a6f
2 touches
0 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
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 0x72083f0d9f…8e082a
Audit this contract →
← previous block·next block →recent activity