← previous blocknext block →recent activity
Analyzing
Block #87,056,101
14 transactions · 11 stateful · 2026-07-11 12:42:30 UTC
Parallelism
57/100
Blocked
45%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,056,101 · 14 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
2w03w14w25w39w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1ab
0xb1dbf0…c0d3
6 touches
3 conflicts
0x80a736f3…3442
0xb1dbf0…c0d3
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x43db9f49…ac4d
0x34b655…2a6f
4 touches
1 conflict
0x47f2ebac…89c1
0x34b655…2a6f
4 touches
1 conflict
0x5172e25d…0a19
0x34b655…2a6f
4 touches
1 conflict
0x52163873…f09f
0x34b655…2a6f
4 touches
1 conflict
0x5a540c99…9b40
0x34b655…2a6f
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
3 conflicts on slot 0x8a35acfbc1…6bd1ab
Audit this contract →
← previous block·next block →recent activity