← previous blocknext block →recent activity
Analyzing
Block #85,674,178
17 transactions · 17 stateful · 2026-07-05 02:52:09 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,674,178 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w012w113w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1aaf4996…65ec
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x192b8d02…75ce
0x34b655…2a6f
4 touches
1 conflict
0x9fa5ad06…5430
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0xde8386f6…bad9
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
6 conflicts on slot 0x1aaf499609…4665ec
Audit this contract →
← previous block·next block →recent activity