← previous blocknext block →recent activity
Analyzing
Block #86,049,639
38 transactions · 30 stateful · 2026-07-06 20:36:15 UTC
Parallelism
87/100
Blocked
40%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,049,639 · 38 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
1w010w011w112w213w324w025w126w227w328w029w130w332w133w234w335w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47d4745e…02bb
0x336ed4…c59c
8 touches
6 conflicts
0x00000000…000a
0x90c374…be45
8 touches
6 conflicts
0x00000000…000b
0x90c374…be45
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x34443913…cbf3
0x336ed4…c59c
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x2dc55ab4…4ff2
0x34b655…2a6f
4 touches
1 conflict
0x3b9bb58c…e73a
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: 0x336ed437…cfc59c
6 conflicts on slot 0x47d4745e02…9002bb
Audit this contract →
← previous block·next block →recent activity