← previous blocknext block →recent activity
Analyzing
Block #87,418,774
10 transactions · 8 stateful · 2026-07-13 05:07:46 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,418,774 · 10 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
1w02w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x264f7d7d…8444
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
4 touches
1 conflict
0xa457c06e…2f06
0x34b655…2a6f
4 touches
1 conflict
0xe47478a3…a058
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x0725ad1d…a03f
0x34b655…2a6f
4 touches
1 conflict
0x0a6ba3b4…2123
0x34b655…2a6f
4 touches
1 conflict
0x114a5fe9…8d41
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
3 conflicts on slot 0x264f7d7d7c…ee8444
Audit this contract →
← previous block·next block →recent activity