← previous blocknext block →recent activity
Analyzing
Block #86,628,998
23 transactions · 18 stateful · 2026-07-09 13:07:23 UTC
Parallelism
78/100
Blocked
44%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,628,998 · 23 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
3w04w17w29w310w411w017w018w119w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x4a92f8…f3d6
10 touches
10 conflicts
0x4a4c3d20…bd65
0x3bd359…433a
10 touches
10 conflicts
0x0db0aaac…e94d
0x43cf54…7777
10 touches
10 conflicts
0x00000000…0001
0x4a92f8…f3d6
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xfe2b47…c052
4 touches
1 conflict
0x08102aaf…36b2
0x34b655…2a6f
4 touches
1 conflict
0x3d2c514e…49b1
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: 0x4a92f8d9…13f3d6
10 conflicts on slot 0x0000000000…000000
Audit this contract →
← previous block·next block →recent activity