← previous blocknext block →recent activity
Analyzing
Block #86,194,075
22 transactions · 21 stateful · 2026-07-07 12:40:04 UTC
Parallelism
68/100
Blocked
52%
Avg conflicts / tx
1.23
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,194,075 · 22 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
1w02w04w17w28w211w212w113w116w017w118w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0xcf7bbede…8ca1
0x34b655…2a6f
5 touches
3 conflicts
0x213a54fa…c85f
0x34b655…2a6f
4 touches
1 conflict
0x49c1b7da…2c47
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x72470f81…c402
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity