← previous blocknext block →recent activity
Analyzing
Block #87,624,208
16 transactions · 16 stateful · 2026-07-14 04:02:21 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
1.81
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,624,208 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w16w27w38w49w511w112w513w615w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x4c188934…158e
0x34b655…2a6f
8 touches
6 conflicts
0xc514314c…1aa4
0x34b655…2a6f
8 touches
6 conflicts
0xc6ed530e…fa7d
0x34b655…2a6f
8 touches
6 conflicts
0x536588d3…19c5
0x34b655…2a6f
6 touches
3 conflicts
0x1f40ac22…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x5cdc6d5c…d604
0x34b655…2a6f
6 touches
3 conflicts
0x6794cf6c…5b53
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity