← previous blocknext block →recent activity
Analyzing
Block #87,703,210
18 transactions · 16 stateful · 2026-07-14 12:50:31 UTC
Parallelism
89/100
Blocked
25%
Avg conflicts / tx
0.28
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,703,210 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w19w010w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6b873a5…cffb
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xae8ff4a3…733f
0x34b655…2a6f
4 touches
1 conflict
0xb6ed530c…d450
0x34b655…2a6f
4 touches
1 conflict
0x7d3c50c5…2279
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf094e5be…d695
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0001
0xc1ff9f…b0fc
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
1 conflict on slot 0xa6b873a552…cbcffb
Audit this contract →
← previous block·next block →recent activity