← previous blocknext block →recent activity
Analyzing
Block #87,313,536
19 transactions · 18 stateful · 2026-07-12 17:23:53 UTC
Parallelism
89/100
Blocked
17%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,313,536 · 19 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
2w04w07w19w112w015w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa013ecc1…7c8f
0x34b655…2a6f
4 touches
1 conflict
0xa05444cf…cd70
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xb91a6f59…722c
0x34b655…2a6f
4 touches
1 conflict
0x38948e75…437a
0x34b655…2a6f
2 touches
0 conflicts
0x41ebf7ed…f662
0x34b655…2a6f
2 touches
0 conflicts
0x442dc980…b7ca
0x34b655…2a6f
2 touches
0 conflicts
0x8b87ece6…3353
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 0xa013ecc17b…017c8f
Audit this contract →
← previous block·next block →recent activity