← previous blocknext block →recent activity
Analyzing
Block #86,947,087
16 transactions · 14 stateful · 2026-07-11 00:34:03 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,947,087 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1ad
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1ae
0xb1dbf0…c0d3
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x9d1bb389…c7d9
0xb1dbf0…c0d3
3 touches
1 conflict
0x0335ae80…8414
0xb1dbf0…c0d3
3 touches
1 conflict
0xe6756f63…5e1f
0x40c49f…2af0
2 touches
0 conflicts
0xeee2956b…ccb8
0x40c49f…2af0
2 touches
0 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: 0xb1dbf05f…b1c0d3
1 conflict on slot 0x8a35acfbc1…6bd1ad
Audit this contract →
← previous block·next block →recent activity