← previous blocknext block →recent activity
Analyzing
Block #86,447,085
14 transactions · 13 stateful · 2026-07-08 16:49:56 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,447,085 · 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
1w02w13w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5a1a5cb…5ca1
0x34b655…2a6f
4 touches
1 conflict
0xb6ed530c…d450
0x34b655…2a6f
4 touches
1 conflict
0xee4fe1f7…3ead
0x34b655…2a6f
4 touches
1 conflict
0x16314c2d…3a92
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x2d8af94a…722c
0x34b655…2a6f
2 touches
0 conflicts
0x616c7c23…14e7
0x34b655…2a6f
2 touches
0 conflicts
0x65e795ca…0320
0x34b655…2a6f
2 touches
0 conflicts
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 0xe5a1a5cb00…a05ca1
Audit this contract →
← previous block·next block →recent activity