← previous blocknext block →recent activity
Analyzing
Block #85,174,510
14 transactions · 13 stateful · 2026-07-02 19:24:40 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,174,510 · 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
4w05w16w210w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf660c7f6…1f74
0x34b655…2a6f
4 touches
1 conflict
0x287ee95e…0034
0x34b655…2a6f
4 touches
1 conflict
0x32409e80…a396
0x34b655…2a6f
4 touches
1 conflict
0x74cdbba7…a524
0x34b655…2a6f
4 touches
1 conflict
0x7e1c758b…2f47
0x34b655…2a6f
4 touches
1 conflict
0xb04d17a0…10e8
0x34b655…2a6f
4 touches
1 conflict
0xbf09519c…1bfe
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0xf660c7f6cc…381f74
Audit this contract →
← previous block·next block →recent activity