← previous blocknext block →recent activity
Analyzing
Block #85,523,788
16 transactions · 12 stateful · 2026-07-04 10:10:47 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,523,788 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfca3cd0…5023
0x34b655…2a6f
4 touches
1 conflict
0xf4150f34…bfea
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0xa9b70d7c…76c0
0xd32edf…ff58
3 touches
1 conflict
0x0c69ffc0…c04a
0x065c9d…c394
2 touches
0 conflicts
0x13eff0b7…de5d
0x065c9d…c394
2 touches
0 conflicts
0x62027550…dfd1
0x065c9d…c394
2 touches
0 conflicts
0x7d3d1789…fa9c
0x065c9d…c394
2 touches
0 conflicts
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 0xbfca3cd067…cd5023
Audit this contract →
← previous block·next block →recent activity