← previous blocknext block →recent activity
Analyzing
Block #87,310,759
23 transactions · 22 stateful · 2026-07-12 17:05:20 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,310,759 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w07w08w111w012w113w114w215w116w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x06f3ebf4…8de1
0x34b655…2a6f
4 touches
1 conflict
0x167f697f…7f61
0x34b655…2a6f
4 touches
1 conflict
0x167f697f…7f62
0x34b655…2a6f
4 touches
1 conflict
0x18fe7fdc…77f7
0x34b655…2a6f
4 touches
1 conflict
0x4a439abd…eaf4
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
3 conflicts on slot 0x64aaadbf0a…79f9f3
Audit this contract →
← previous block·next block →recent activity