← previous blocknext block →recent activity
Analyzing
Block #85,773,332
10 transactions · 9 stateful · 2026-07-05 13:53:38 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,773,332 · 10 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
1w02w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0a6f5e37…6c3c
0x34b655…2a6f
2 touches
0 conflicts
0x2b8ae238…b119
0x34b655…2a6f
2 touches
0 conflicts
0x2d48f548…cdd5
0x34b655…2a6f
2 touches
0 conflicts
0x326d4924…1788
0x34b655…2a6f
2 touches
0 conflicts
0x37d2d6e6…356d
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity