← previous blocknext block →recent activity
Analyzing
Block #86,082,513
21 transactions · 20 stateful · 2026-07-07 00:15:20 UTC
Parallelism
81/100
Blocked
45%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,082,513 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w19w210w112w013w114w217w018w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
6 touches
3 conflicts
0x42041fec…bd86
0x754704…b603
6 touches
3 conflicts
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0x39ab5ddf…8a72
0x34b655…2a6f
4 touches
1 conflict
0x87d1b778…dcfe
0x34b655…2a6f
4 touches
1 conflict
0x9361e3b2…3bff
0x34b655…2a6f
4 touches
1 conflict
0xbcc5ae85…6ba2
0xa6afd3…d132
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: Perpl
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity