← previous blocknext block →recent activity
Analyzing
Block #86,957,796
9 transactions · 8 stateful · 2026-07-11 01:45:36 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,957,796 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb07a0849…3b62
0xb1dbf0…c0d3
4 touches
1 conflict
0xce3de73c…ae36
0x34b655…2a6f
4 touches
1 conflict
0x6286219a…0721
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d19c
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1ac
0xb1dbf0…c0d3
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x1628bc3a…899d
0x34b655…2a6f
4 touches
1 conflict
0x3e4ecdea…20fe
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
1 conflict on slot 0xb07a08497d…d13b62
Audit this contract →
← previous block·next block →recent activity