← previous blocknext block →recent activity
Analyzing
Block #86,794,861
19 transactions · 14 stateful · 2026-07-10 07:36:18 UTC
Parallelism
74/100
Blocked
36%
Avg conflicts / tx
0.26
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,794,861 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w212w313w418w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4984f7be…d515
0x34b655…2a6f
4 touches
1 conflict
0xa6b89ebb…a66e
0x34b655…2a6f
4 touches
1 conflict
0xabb1cfb4…d9dc
0x34b655…2a6f
4 touches
1 conflict
0xcc6e2e88…6569
0x34b655…2a6f
4 touches
1 conflict
0x07d8b1e8…78c6
0x34b655…2a6f
4 touches
1 conflict
0x167de262…f61f
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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 0x4984f7bedd…bfd515
Audit this contract →
← previous block·next block →recent activity