← previous blocknext block →recent activity
Analyzing
Block #85,273,976
22 transactions · 21 stateful · 2026-07-03 06:27:13 UTC
Parallelism
73/100
Blocked
48%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,273,976 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w19w210w112w315w016w117w219w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2de2656d…5bbc
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x42041fec…bd86
0x754704…b603
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x1d61a1c5…9fe6
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xac2a0273…721b
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
3 conflicts on slot 0x2de2656dd0…a95bbc
Audit this contract →
← previous block·next block →recent activity