← previous blocknext block →recent activity
Analyzing
Block #87,667,025
25 transactions · 19 stateful · 2026-07-14 08:48:29 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,667,025 · 25 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
2w03w111w012w113w214w122w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x19caa5cc…17c7
0x34b655…2a6f
4 touches
1 conflict
0x4ec199d4…e9f1
0x34b655…2a6f
4 touches
1 conflict
0x6030bece…bf0e
0x34b655…2a6f
4 touches
1 conflict
0x6778feb2…9734
0x34b655…2a6f
4 touches
1 conflict
0x688ae285…d678
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a3
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity