← previous blocknext block →recent activity
Analyzing
Block #86,456,063
15 transactions · 11 stateful · 2026-07-08 17:49:57 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,456,063 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c6a17fa…e95d
0x34b655…2a6f
4 touches
1 conflict
0xe1d1f14d…3ffb
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0x3a19f834…ff17
0x40c49f…2af0
2 touches
0 conflicts
0x677e8872…cec0
0x40c49f…2af0
2 touches
0 conflicts
0xf47ff7a3…64f4
0x40c49f…2af0
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 0x7c6a17faf8…5be95d
Audit this contract →
← previous block·next block →recent activity