← previous blocknext block →recent activity
Analyzing
Block #85,725,752
11 transactions · 10 stateful · 2026-07-05 08:37:09 UTC
Parallelism
73/100
Blocked
40%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,725,752 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w17w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x505d32fe…14ad
0x34b655…2a6f
6 touches
3 conflicts
0xb4bc16a4…4825
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x510c8ab3…95d5
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5318
0x34b655…2a6f
4 touches
1 conflict
0x4927cdfa…c2f2
0x065c9d…c394
2 touches
0 conflicts
0x4c9a5caf…55ec
0x065c9d…c394
2 touches
0 conflicts
0x82ec1892…68af
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
3 conflicts on slot 0x505d32fe09…f014ad
Audit this contract →
← previous block·next block →recent activity