← previous blocknext block →recent activity
Analyzing
Block #85,898,730
21 transactions · 17 stateful · 2026-07-06 03:48:55 UTC
Parallelism
86/100
Blocked
24%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,898,730 · 21 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
1w02w14w16w07w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc904d2e4…66d0
0x34b655…2a6f
4 touches
1 conflict
0xea88156e…91e5
0x34b655…2a6f
4 touches
1 conflict
0xb0b4edfd…a152
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
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
1 conflict on slot 0xc904d2e45e…c266d0
Audit this contract →
← previous block·next block →recent activity