← previous blocknext block →recent activity
Analyzing
Block #85,580,554
9 transactions · 9 stateful · 2026-07-04 16:28:48 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,580,554 · 9 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
1w02w13w07w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x213a54fa…c85f
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x05edf2cf…ac3c
0x34b655…2a6f
4 touches
1 conflict
0x10d9dbcb…9fdb
0x34b655…2a6f
4 touches
1 conflict
0x594c318b…c3d2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x408d584a…8309
0x34b655…2a6f
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 0x213a54fa2e…2fc85f
Audit this contract →
← previous block·next block →recent activity