← previous blocknext block →recent activity
Analyzing
Block #87,920,003
25 transactions · 24 stateful · 2026-07-15 13:00:53 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,920,003 · 25 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
1w02w13w24w35w47w08w19w010w112w216w217w318w424w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000b
0x90c374…be45
10 touches
10 conflicts
0xc88f593e…5d93
0x336ed4…c59c
10 touches
10 conflicts
0x00000000…000a
0x90c374…be45
10 touches
10 conflicts
0x165b3a0d…8987
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x93c58e4d…9b32
0x336ed4…c59c
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x47d4745e…02bb
0x336ed4…c59c
6 touches
3 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: 0x90c3747c…0ebe45
10 conflicts on slot 0x0000000000…00000b
Audit this contract →
← previous block·next block →recent activity