← previous blocknext block →recent activity
Analyzing
Block #87,497,461
46 transactions · 34 stateful · 2026-07-13 13:53:53 UTC
Parallelism
72/100
Blocked
62%
Avg conflicts / tx
1.72
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,497,461 · 46 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w113w014w118w019w125w227w328w430w531w632w233w634w735w837w239w740w841w943w1144w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0xcfcb8911…e9da
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0x326d4924…1788
0x34b655…2a6f
10 touches
10 conflicts
0x7b2f3e6d…978f
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity