← previous blocknext block →recent activity
Analyzing
Block #85,914,671
25 transactions · 19 stateful · 2026-07-06 05:35:06 UTC
Parallelism
84/100
Blocked
42%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,914,671 · 25 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
1w02w14w05w16w210w011w112w015w222w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10a2bd5d…ad6d
0x8d1565…6723
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
6 touches
3 conflicts
0x93c58e4d…9b32
0x336ed4…c59c
6 touches
3 conflicts
0x00000000…000a
0x90c374…be45
6 touches
3 conflicts
0x353a3a00…5e0a
0x34b655…2a6f
4 touches
1 conflict
0x1aaf4996…65ec
0x34b655…2a6f
4 touches
1 conflict
0x747f609d…1555
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: 0x8d156514…236723
3 conflicts on slot 0x10a2bd5d43…51ad6d
Audit this contract →
← previous block·next block →recent activity