← previous blocknext block →recent activity
Analyzing
Block #85,281,940
11 transactions · 11 stateful · 2026-07-03 07:20:15 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,281,940 · 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
1w02w15w06w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2de2656d…5bbc
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00aa6163…15df
0x34b655…2a6f
4 touches
1 conflict
0xf3f78dcd…2838
0x065c9d…c394
2 touches
0 conflicts
0xf45144e7…5a24
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x2de2656dd0…a95bbc
Audit this contract →
← previous block·next block →recent activity