← previous blocknext block →recent activity
Analyzing
Block #87,614,721
24 transactions · 21 stateful · 2026-07-14 02:58:56 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,614,721 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w08w09w110w111w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3439dfbc…0d03
0x34b655…2a6f
8 touches
6 conflicts
0x19e9a11b…e981
0x34b655…2a6f
8 touches
6 conflicts
0x71806e15…2893
0x34b655…2a6f
6 touches
3 conflicts
0x9c3004b2…5421
0x34b655…2a6f
6 touches
3 conflicts
0x4f1e16d4…4833
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
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 0x3439dfbcc6…080d03
Audit this contract →
← previous block·next block →recent activity