← previous blocknext block →recent activity
Analyzing
Block #86,453,498
25 transactions · 20 stateful · 2026-07-08 17:32:49 UTC
Parallelism
72/100
Blocked
35%
Avg conflicts / tx
0.68
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,453,498 · 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
2w08w010w111w015w117w218w319w420w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x8eb0ac6b…a73a
0x34b655…2a6f
6 touches
3 conflicts
0xeebd31ac…0794
0x34b655…2a6f
5 touches
3 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0x469e824a…d814
0x34b655…2a6f
4 touches
1 conflict
0x649a69ad…f86a
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7ce93f3d…b70e
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity