← previous blocknext block →recent activity
Analyzing
Block #87,517,785
24 transactions · 23 stateful · 2026-07-13 16:09:59 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,517,785 · 24 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
5w06w17w08w19w210w211w313w014w015w116w217w018w019w121w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
8 touches
6 conflicts
0xb4ca3e09…e96b
0x34b655…2a6f
6 touches
3 conflicts
0xd0243b19…507b
0x34b655…2a6f
6 touches
3 conflicts
0xfcea0c54…587f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0001
0xc1ff9f…b0fc
6 touches
3 conflicts
0x6bdc8443…007e
0x34b655…2a6f
4 touches
1 conflict
0x7dcd4444…a924
0x34b655…2a6f
4 touches
1 conflict
0x8578537e…8163
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 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity