← previous blocknext block →recent activity
Analyzing
Block #87,333,446
30 transactions · 26 stateful · 2026-07-12 19:37:05 UTC
Parallelism
77/100
Blocked
46%
Avg conflicts / tx
0.8
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,333,446 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w18w19w212w113w314w215w316w417w321w422w528w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa05444cf…cd70
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x61377ba1…0bef
0xa6afd3…d132
6 touches
3 conflicts
0xad0c145d…72b3
0xa6afd3…d132
6 touches
3 conflicts
0x737acb78…fce8
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: Perpl
6 conflicts on slot 0xa05444cff4…1ecd70
Audit this contract →
← previous block·next block →recent activity