← previous blocknext block →recent activity
Analyzing
Block #87,168,225
21 transactions · 16 stateful · 2026-07-12 01:11:24 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,168,225 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w19w210w311w414w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x152f8e3d…3da0
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x25e3730b…24a9
0x34b655…2a6f
4 touches
1 conflict
0x27b1a71a…458d
0x34b655…2a6f
4 touches
1 conflict
0x53c922c1…1f78
0x34b655…2a6f
4 touches
1 conflict
0x64420f3d…07e3
0x34b655…2a6f
4 touches
1 conflict
0x6e27bdfb…108a
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity