← previous blocknext block →recent activity
Analyzing
Block #85,994,487
35 transactions · 21 stateful · 2026-07-06 14:27:46 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,994,487 · 35 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
1w02w13w04w05w119w121w029w030w131w233w334w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x036e7d45…7d9d
0x34b655…2a6f
4 touches
1 conflict
0x2d7e60b7…c173
0x34b655…2a6f
4 touches
1 conflict
0x4d3e58e0…a2d7
0x34b655…2a6f
4 touches
1 conflict
0x6f58168d…ea24
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity