← previous blocknext block →recent activity
Analyzing
Block #86,300,432
24 transactions · 21 stateful · 2026-07-08 00:30:11 UTC
Parallelism
75/100
Blocked
48%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,300,432 · 24 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
1w02w13w05w06w19w210w114w215w316w117w222w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0xfadb0e19…7a27
0x851145…3f07
6 touches
3 conflicts
0x93d4b4e9…5daa
0x851145…3f07
4 touches
1 conflict
0x0bd95eb4…e562
0x34b655…2a6f
4 touches
1 conflict
0x69ce640b…884a
0x34b655…2a6f
4 touches
1 conflict
0x8cd684d0…c3cb
0x34b655…2a6f
4 touches
1 conflict
0x9165b7f6…c006
0x34b655…2a6f
4 touches
1 conflict
0x966e45cf…0f25
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: 0x851145ea…9f3f07
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity