← previous blocknext block →recent activity
Analyzing
Block #85,913,336
16 transactions · 14 stateful · 2026-07-06 05:26:12 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,913,336 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w08w19w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6884b1c…8b7f
0x34b655…2a6f
4 touches
1 conflict
0xb96c408d…7113
0x34b655…2a6f
4 touches
1 conflict
0xbb12db23…857e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x1aaf4996…65ec
0x34b655…2a6f
4 touches
1 conflict
0x28287367…f0f5
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
1 conflict on slot 0xf6884b1c10…e88b7f
Audit this contract →
← previous block·next block →recent activity