← previous blocknext block →recent activity
Analyzing
Block #87,348,874
32 transactions · 30 stateful · 2026-07-12 21:20:13 UTC
Parallelism
53/100
Blocked
67%
Avg conflicts / tx
2.72
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,348,874 · 32 txs across 15 waves · depth 15
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
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w28w39w412w213w314w515w116w217w623w724w825w926w1027w1129w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0x6e1cd42e…1f23
0x34b655…2a6f
12 touches
15 conflicts
0x0c9eb6ea…7c39
0x34b655…2a6f
12 touches
15 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
8 touches
6 conflicts
0x71658d1a…f1ec
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity