← previous blocknext block →recent activity
Analyzing
Block #87,525,015
16 transactions · 13 stateful · 2026-07-13 16:58:51 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,525,015 · 16 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
2w03w14w25w06w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0x4d66de6b…202b
0x34b655…2a6f
6 touches
3 conflicts
0x78346476…4311
0x34b655…2a6f
6 touches
3 conflicts
0x4f2fabb0…9b09
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0001
0xc1ff9f…b0fc
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x92e28bd4…72cc
0x34b655…2a6f
4 touches
1 conflict
0xc26f47c1…3264
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
3 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity