← previous blocknext block →recent activity
Analyzing
Block #85,136,767
21 transactions · 16 stateful · 2026-07-02 15:13:20 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,136,767 · 21 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
1w02w13w25w08w09w114w115w316w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed296a95…7d12
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x3e1c3586…83d7
0xa6afd3…d132
6 touches
3 conflicts
0x9cc13b7b…c0ac
0xa6afd3…d132
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x3c56d6ef…31cd
0x34b655…2a6f
4 touches
1 conflict
0x656bd53e…af4e
0x34b655…2a6f
4 touches
1 conflict
0x79fade94…7f93
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
3 conflicts on slot 0xed296a9543…ef7d12
Audit this contract →
← previous block·next block →recent activity