← previous blocknext block →recent activity
Analyzing
Block #85,372,278
19 transactions · 17 stateful · 2026-07-03 17:22:05 UTC
Parallelism
89/100
Blocked
24%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,372,278 · 19 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
2w06w08w09w110w111w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261c40aa…b133
0x34b655…2a6f
4 touches
1 conflict
0x9fb55ee7…8ecc
0xa6afd3…d132
4 touches
1 conflict
0x8a751d7a…247c
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
1 conflict on slot 0x261c40aab5…3bb133
Audit this contract →
← previous block·next block →recent activity