← previous blocknext block →recent activity
Analyzing
Block #87,643,328
18 transactions · 16 stateful · 2026-07-14 06:10:10 UTC
Parallelism
78/100
Blocked
19%
Avg conflicts / tx
0.22
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,643,328 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w111w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0xf7bf2a6e…1224
0x34b655…2a6f
4 touches
1 conflict
0xd97c2fdb…27d5
0x34b655…2a6f
4 touches
1 conflict
0xf7bf2a6e…1223
0x34b655…2a6f
4 touches
1 conflict
0x94b8e9d6…77d6
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xcfbd4fbb…e2b4
0x34b655…2a6f
4 touches
1 conflict
0x687aa38a…8663
0x34b655…2a6f
3 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
3 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity