← previous blocknext block →recent activity
Analyzing
Block #87,419,902
14 transactions · 13 stateful · 2026-07-13 05:15:18 UTC
Parallelism
64/100
Blocked
46%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,419,902 · 14 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
2w03w14w06w17w28w311w413w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xc6ed530e…fa7d
0x34b655…2a6f
8 touches
6 conflicts
0x934da4f1…43a7
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xb6dd5be0…26d6
0x34b655…2a6f
6 touches
3 conflicts
0x6e0ee2ba…7b1f
0x34b655…2a6f
4 touches
1 conflict
0x73da1e9b…2d36
0x34b655…2a6f
4 touches
1 conflict
0x73da1e9b…2d37
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity