← previous blocknext block →recent activity
Analyzing
Block #86,251,473
26 transactions · 23 stateful · 2026-07-07 19:03:31 UTC
Parallelism
85/100
Blocked
48%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,251,473 · 26 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
1w02w15w16w27w09w111w212w015w217w018w119w320w022w023w124w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23a320fb…cbd7
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3ccc04c4…effd
0xd32edf…ff58
5 touches
3 conflicts
0x1a5d321d…a474
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x77ed432f…fa04
0x065c9d…c394
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 0x23a320fbfb…26cbd7
Audit this contract →
← previous block·next block →recent activity