← previous blocknext block →recent activity
Analyzing
Block #86,452,101
9 transactions · 9 stateful · 2026-07-08 17:23:28 UTC
Parallelism
56/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,452,101 · 9 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
2w04w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x72470f81…c402
0x34b655…2a6f
4 touches
1 conflict
0xdb86d50f…b5fc
0x34b655…2a6f
4 touches
1 conflict
0x754e4238…cdf3
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5ea
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5eb
0x34b655…2a6f
4 touches
1 conflict
0xa557ac1c…22f4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity