← previous blocknext block →recent activity
Analyzing
Block #87,409,841
14 transactions · 11 stateful · 2026-07-13 04:07:59 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
1.07
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,409,841 · 14 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
1w02w13w04w05w16w27w310w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1ad
0xb1dbf0…c0d3
8 touches
6 conflicts
0x8a35acfb…d1ae
0xb1dbf0…c0d3
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x086db8fc…0024
0x34b655…2a6f
6 touches
3 conflicts
0x801058a8…5bc3
0x34b655…2a6f
6 touches
3 conflicts
0xce64bd05…a2d6
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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: 0xb1dbf05f…b1c0d3
6 conflicts on slot 0x8a35acfbc1…6bd1ad
Audit this contract →
← previous block·next block →recent activity