← previous blocknext block →recent activity
Analyzing
Block #87,585,246
17 transactions · 13 stateful · 2026-07-13 23:41:48 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,585,246 · 17 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
1w02w110w011w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe3b7538…cdbd
0x34b655…2a6f
4 touches
1 conflict
0xdc19d35a…1aaf
0x34b655…2a6f
4 touches
1 conflict
0xdcf93b63…ae96
0x34b655…2a6f
4 touches
1 conflict
0xfa34d3be…9380
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x4b8532b7…d8f9
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 0xfe3b7538b8…aecdbd
Audit this contract →
← previous block·next block →recent activity