← previous blocknext block →recent activity
Analyzing
Block #87,613,321
14 transactions · 11 stateful · 2026-07-14 02:49:33 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,613,321 · 14 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
3w04w16w27w38w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab5e4a7a…6db0
0x34b655…2a6f
4 touches
1 conflict
0xab5e4a7a…6db1
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd3fde67c…9379
0x34b655…2a6f
4 touches
1 conflict
0xe7d2a532…f5a5
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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
1 conflict on slot 0xab5e4a7a8e…af6db0
Audit this contract →
← previous block·next block →recent activity