← previous blocknext block →recent activity
Analyzing
Block #87,709,232
30 transactions · 21 stateful · 2026-07-14 13:30:53 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,709,232 · 30 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
1w05w07w09w112w213w014w115w116w119w321w423w027w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3c8642a…7da5
0x2a68ba…90c5
8 touches
6 conflicts
0xce827910…ff22
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xd76a23f3…c494
0x065c9d…c394
5 touches
3 conflicts
0x64c786c3…fed8
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0000
0x2d82ac…5fd8
4 touches
1 conflict
0x8e80434a…a96d
0x0555e3…2b9c
4 touches
1 conflict
0x8a2f9a36…fb4a
0x2d82ac…5fd8
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: Kuru Exchange: MarginAccount
6 conflicts on slot 0xc3c8642ae9…317da5
Audit this contract →
← previous block·next block →recent activity