← previous blocknext block →recent activity
Analyzing
Block #85,170,817
23 transactions · 19 stateful · 2026-07-02 19:00:03 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,170,817 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w08w09w110w211w314w215w016w117w218w322w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7bc74ef3…0fee
0x34b655…2a6f
8 touches
6 conflicts
0xf79df061…e005
0xe52b14…7230
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xa457c06e…2f06
0x34b655…2a6f
6 touches
3 conflicts
0x16b3a441…13db
0x34b655…2a6f
6 touches
3 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
6 touches
3 conflicts
0xa1144aa9…7f67
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 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
6 conflicts on slot 0x7bc74ef3d1…f60fee
Audit this contract →
← previous block·next block →recent activity