← previous blocknext block →recent activity
Analyzing
Block #86,853,024
29 transactions · 24 stateful · 2026-07-10 14:05:14 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.62
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,853,024 · 29 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w19w010w113w015w016w123w224w325w426w527w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x08330b36…ae29
0x34b655…2a6f
6 touches
3 conflicts
0xec63e4f6…4778
0x34b655…2a6f
6 touches
3 conflicts
0x99f666e3…b2a2
0x3bd359…433a
4 touches
1 conflict
0xf8127de7…d5ec
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x47bae1…7568
4 touches
1 conflict
0x00000000…0002
0x47bae1…7568
4 touches
1 conflict
0x00000000…0004
0x47bae1…7568
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity