← previous blocknext block →recent activity
Analyzing
Block #87,594,357
14 transactions · 12 stateful · 2026-07-14 00:42:45 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,594,357 · 14 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
1w04w05w16w27w113w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3f008b3…b7c9
0x34b655…2a6f
8 touches
6 conflicts
0x62bd1793…0097
0x34b655…2a6f
6 touches
3 conflicts
0xc5f336ca…912e
0x34b655…2a6f
4 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0x3fc40870…7ef4
0x34b655…2a6f
4 touches
1 conflict
0x410b84ab…1dbc
0x34b655…2a6f
4 touches
1 conflict
0x6f761690…95bd
0x34b655…2a6f
4 touches
1 conflict
0xa0bc9ef1…59a0
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 0xb3f008b3b9…6ab7c9
Audit this contract →
← previous block·next block →recent activity