← previous blocknext block →recent activity
Analyzing
Block #87,580,866
13 transactions · 11 stateful · 2026-07-13 23:12:31 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,580,866 · 13 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
4w05w08w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea0fee48…1fab
0x34b655…2a6f
4 touches
1 conflict
0xd42fdceb…d869
0x34b655…2a6f
4 touches
1 conflict
0xd42fdceb…d86a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfee21213…72fd
0x34b655…2a6f
4 touches
1 conflict
0x5ad8135f…d8e6
0x34b655…2a6f
4 touches
1 conflict
0x17a9c250…ede7
0x34b655…2a6f
3 touches
1 conflict
0x46279ae7…20dd
0x2b46c0…1669
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 0xea0fee482c…b91fab
Audit this contract →
← previous block·next block →recent activity