← previous blocknext block →recent activity
Analyzing
Block #86,350,543
22 transactions · 18 stateful · 2026-07-08 06:04:54 UTC
Parallelism
64/100
Blocked
44%
Avg conflicts / tx
1.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,350,543 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
10w011w113w014w115w216w317w418w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x9385d07d…4829
0x34b655…2a6f
6 touches
3 conflicts
0x16a8cd0c…27bd
0x34b655…2a6f
6 touches
3 conflicts
0x96dd83e6…a507
0x34b655…2a6f
6 touches
3 conflicts
0xcc6e2e88…6569
0x34b655…2a6f
6 touches
3 conflicts
0x61592964…8b88
0x34b655…2a6f
6 touches
3 conflicts
0x8d0e98f3…7ba0
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity