← previous blocknext block →recent activity
Analyzing
Block #86,387,946
15 transactions · 14 stateful · 2026-07-08 10:14:59 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,387,946 · 15 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
1w02w13w04w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5d176f56…e5fb
0xd32edf…ff58
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0a82a450…cd34
0x065c9d…c394
2 touches
0 conflicts
0x16ef220e…396f
0x065c9d…c394
2 touches
0 conflicts
0x473ae626…70b8
0x065c9d…c394
2 touches
0 conflicts
0x4901bf46…b2a1
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 0x4d4389b20d…b56e07
Audit this contract →
← previous block·next block →recent activity