← previous blocknext block →recent activity
Analyzing
Block #86,455,533
25 transactions · 20 stateful · 2026-07-08 17:46:25 UTC
Parallelism
72/100
Blocked
60%
Avg conflicts / tx
1.12
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,455,533 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w38w09w110w211w312w413w515w323w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xe6805ef8…e22e
0x34b655…2a6f
6 touches
3 conflicts
0x37d710c8…45c1
0x34b655…2a6f
4 touches
1 conflict
0x3f2c003a…6d74
0x34b655…2a6f
4 touches
1 conflict
0x4b2d32d9…afe1
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: Perpl
15 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity