← previous blocknext block →recent activity
Analyzing
Block #86,929,633
18 transactions · 16 stateful · 2026-07-10 22:37:26 UTC
Parallelism
89/100
Blocked
6%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,929,633 · 18 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4fa2386a…7e34
0x34b655…2a6f
4 touches
1 conflict
0x2efd1517…0726
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x96c303ae…c7ef
0x34b655…2a6f
4 touches
1 conflict
0x4fa2386a…7e33
0x34b655…2a6f
4 touches
1 conflict
0x43d14af2…b5c8
0x34b655…2a6f
3 touches
1 conflict
0x90a021f0…f922
0x34b655…2a6f
2 touches
0 conflicts
0xac2a0273…7212
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 0x4fa2386ada…fa7e34
Audit this contract →
← previous block·next block →recent activity