← previous blocknext block →recent activity
Analyzing
Block #87,593,398
21 transactions · 19 stateful · 2026-07-14 00:36:20 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,593,398 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w09w110w211w112w013w315w116w219w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc514314c…1aa4
0x34b655…2a6f
8 touches
6 conflicts
0xc6ed530e…fa7d
0x34b655…2a6f
6 touches
3 conflicts
0xd97c2fdb…27d5
0x34b655…2a6f
6 touches
3 conflicts
0xea4316bc…6b4f
0x34b655…2a6f
6 touches
3 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x342fbbca…d443
0x40c49f…2af0
6 touches
3 conflicts
0x952e910f…0001
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xc514314ca6…fa1aa4
Audit this contract →
← previous block·next block →recent activity