← previous blocknext block →recent activity
Analyzing
Block #86,055,552
13 transactions · 13 stateful · 2026-07-06 21:15:39 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,055,552 · 13 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
2w03w14w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x65903ef9…2567
0x34b655…2a6f
4 touches
1 conflict
0xdb0d6a04…ab4e
0x34b655…2a6f
4 touches
1 conflict
0xdfb97a89…abc8
0x34b655…2a6f
4 touches
1 conflict
0xe3716626…7d68
0x34b655…2a6f
4 touches
1 conflict
0xfd42a6b9…4c81
0x34b655…2a6f
4 touches
1 conflict
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity