← previous blocknext block →recent activity
Analyzing
Block #85,898,414
19 transactions · 16 stateful · 2026-07-06 03:46:48 UTC
Parallelism
68/100
Blocked
38%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,898,414 · 19 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
4w06w18w09w114w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
6 touches
3 conflicts
0x6bdb9869…7558
0x34b655…2a6f
4 touches
1 conflict
0x7cee1be1…e770
0x34b655…2a6f
4 touches
1 conflict
0x97b0b2ee…4666
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
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
6 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity