← previous blocknext block →recent activity
Analyzing
Block #86,921,911
26 transactions · 20 stateful · 2026-07-10 21:45:50 UTC
Parallelism
81/100
Blocked
55%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,921,911 · 26 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
2w03w14w05w16w28w39w411w012w115w216w117w218w324w025w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
10 touches
10 conflicts
0x7babfe9a…ff96
0x34b655…2a6f
6 touches
3 conflicts
0x3a76803c…4181
0x34b655…2a6f
6 touches
3 conflicts
0x11589c8d…51b8
0x34b655…2a6f
4 touches
1 conflict
0x2885cd6f…0d9b
0x34b655…2a6f
4 touches
1 conflict
0x45597879…8174
0x34b655…2a6f
4 touches
1 conflict
0x5a19ef35…dc70
0x34b655…2a6f
4 touches
1 conflict
0x757b0543…e087
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: 0x04fdeac2…f747d7
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity