← previous blocknext block →recent activity
Analyzing
Block #87,580,636
18 transactions · 14 stateful · 2026-07-13 23:10:58 UTC
Parallelism
89/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,580,636 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w013w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ee4a6d2…6389
0x34b655…2a6f
4 touches
1 conflict
0x42341814…60f1
0x34b655…2a6f
4 touches
1 conflict
0xd7fe05cd…207e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x04c1786f…3ee6
0x34b655…2a6f
2 touches
0 conflicts
0x07f69062…03ec
0x34b655…2a6f
2 touches
0 conflicts
0x0caac81d…a6f7
0x34b655…2a6f
2 touches
0 conflicts
0x157dbfb2…4089
0x34b655…2a6f
2 touches
0 conflicts
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 0x1ee4a6d212…536389
Audit this contract →
← previous block·next block →recent activity