← previous blocknext block →recent activity
Analyzing
Block #85,523,593
22 transactions · 13 stateful · 2026-07-04 10:09:29 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,523,593 · 22 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
1w06w18w113w015w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd4227d4…c28d
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xd1a6e86d…819b
0x065c9d…c394
3 touches
1 conflict
0x7a12283f…b18a
0x69df8a…6292
2 touches
0 conflicts
0x915c095e…c1e5
0x69df8a…6292
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 0xcd4227d49b…1bc28d
Audit this contract →
← previous block·next block →recent activity