← previous blocknext block →recent activity
Analyzing
Block #86,659,603
19 transactions · 17 stateful · 2026-07-09 16:33:12 UTC
Parallelism
63/100
Blocked
35%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,659,603 · 19 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
10w011w112w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x170e4e4c…2b90
0x34b655…2a6f
4 touches
1 conflict
0x19506cd3…b2cd
0x34b655…2a6f
4 touches
1 conflict
0x2362b8af…c01d
0x34b655…2a6f
4 touches
1 conflict
0x2ac20975…8842
0x34b655…2a6f
4 touches
1 conflict
0x334649c0…069e
0x34b655…2a6f
4 touches
1 conflict
0x3ab029bc…21f7
0x34b655…2a6f
4 touches
1 conflict
0x3bdd71a2…b6eb
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity