← previous blocknext block →recent activity
Analyzing
Block #85,496,354
14 transactions · 13 stateful · 2026-07-04 07:08:16 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,496,354 · 14 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
2w07w08w19w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea4316bc…6b4f
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xa8c7f78e…5815
0x40c49f…2af0
4 touches
1 conflict
0x009177df…4ecc
0x34b655…2a6f
2 touches
0 conflicts
0x0708d53e…d542
0x34b655…2a6f
2 touches
0 conflicts
0x0e04c4cc…551a
0x34b655…2a6f
2 touches
0 conflicts
0x13765c09…9797
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 0xea4316bcc7…a66b4f
Audit this contract →
← previous block·next block →recent activity