← previous blocknext block →recent activity
Analyzing
Block #86,194,328
10 transactions · 8 stateful · 2026-07-07 12:41:43 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,194,328 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5f244d5…f550
0x34b655…2a6f
4 touches
1 conflict
0xe26aee7b…f52b
0x34b655…2a6f
4 touches
1 conflict
0xe8eae8a3…bacc
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0x885a2c62…3178
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
0x34b655…2a6f
4 touches
1 conflict
0x9c325401…848b
0x065c9d…c394
2 touches
0 conflicts
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 0xb5f244d5d7…d9f550
Audit this contract →
← previous block·next block →recent activity