← previous blocknext block →recent activity
Analyzing
Block #87,597,000
16 transactions · 12 stateful · 2026-07-14 01:00:26 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,597,000 · 16 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
2w08w19w010w211w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xc8304415…4f91
0x34b655…2a6f
6 touches
3 conflicts
0x301e1c77…9e30
0x34b655…2a6f
4 touches
1 conflict
0x326f2a00…a2a6
0x34b655…2a6f
4 touches
1 conflict
0x3302b65c…74d5
0x34b655…2a6f
4 touches
1 conflict
0x34ec33e3…2ff4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity