← previous blocknext block →recent activity
Analyzing
Block #85,124,568
24 transactions · 19 stateful · 2026-07-02 13:51:50 UTC
Parallelism
71/100
Blocked
58%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,124,568 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w08w19w214w315w418w220w321w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x62552882…2f5d
0x34b655…2a6f
4 touches
1 conflict
0x63da0619…7a55
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity