← previous blocknext block →recent activity
Analyzing
Block #86,749,130
14 transactions · 13 stateful · 2026-07-10 02:31:01 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,749,130 · 14 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
1w02w14w08w19w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xb21e8ab2…9ca4
0x34b655…2a6f
4 touches
1 conflict
0xbc4e7b49…3d2d
0x34b655…2a6f
4 touches
1 conflict
0xce3de73c…ae35
0x34b655…2a6f
4 touches
1 conflict
0xce3de73c…ae36
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x010d4ce0…8cf0
0x34b655…2a6f
4 touches
1 conflict
0x0f898335…7a89
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
1 conflict on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity