← previous blocknext block →recent activity
Analyzing
Block #86,250,362
12 transactions · 10 stateful · 2026-07-07 18:56:04 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,250,362 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf195ad96…e0c3
0x34b655…2a6f
4 touches
1 conflict
0x23a320fb…cbd7
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x410c62b5…3ac0
0x065c9d…c394
2 touches
0 conflicts
0x3a1e6958…6dc3
0x188d58…ea8e
2 touches
0 conflicts
0x3a1e6958…6dc4
0x188d58…ea8e
2 touches
0 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
2 touches
0 conflicts
0x712df4fd…b828
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xf195ad96b6…00e0c3
Audit this contract →
← previous block·next block →recent activity