← previous blocknext block →recent activity
Analyzing
Block #86,490,141
32 transactions · 23 stateful · 2026-07-08 21:38:00 UTC
Parallelism
84/100
Blocked
30%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,490,141 · 32 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w18w212w013w016w017w123w128w229w030w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
4 touches
1 conflict
0xaba6578d…bd48
0x34b655…2a6f
4 touches
1 conflict
0xce533bff…b9d1
0x34b655…2a6f
4 touches
1 conflict
0xf85bdc12…5dff
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x15a8dcd6…2c36
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