← previous blocknext block →recent activity
Analyzing
Block #87,262,803
12 transactions · 9 stateful · 2026-07-12 11:44:43 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,262,803 · 12 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
1w02w13w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x301e1c77…9e30
0x34b655…2a6f
4 touches
1 conflict
0x3b93aeec…6c4b
0x34b655…2a6f
4 touches
1 conflict
0xd2862d04…388c
0x34b655…2a6f
4 touches
1 conflict
0xf48622ce…c588
0xd32edf…ff58
3 touches
1 conflict
0x5f271d4e…48db
0x065c9d…c394
2 touches
0 conflicts
0xa4f80979…4d71
0x065c9d…c394
2 touches
0 conflicts
0xd35bb5ac…3586
0x065c9d…c394
2 touches
0 conflicts
0xf9e88b63…1f9a
0x065c9d…c394
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 0x301e1c776c…3b9e30
Audit this contract →
← previous block·next block →recent activity