← previous blocknext block →recent activity
Analyzing
Block #85,219,037
10 transactions · 9 stateful · 2026-07-03 00:21:16 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,219,037 · 10 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
2w05w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x70638c24…1553
0x34b655…2a6f
4 touches
1 conflict
0x73e3b124…0f62
0x065c9d…c394
2 touches
0 conflicts
0x8b6d67ec…1ccc
0x065c9d…c394
2 touches
0 conflicts
0xe82d80e6…5337
0x065c9d…c394
2 touches
0 conflicts
0xec68eb3b…6c66
0x065c9d…c394
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity