← previous blocknext block →recent activity
Analyzing
Block #87,418,892
16 transactions · 13 stateful · 2026-07-13 05:08:33 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,418,892 · 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
2w03w14w25w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0xe6043046…5757
0x34b655…2a6f
6 touches
3 conflicts
0xf1e0de4d…eb7f
0x34b655…2a6f
4 touches
1 conflict
0xb568bd0a…0a73
0x34b655…2a6f
4 touches
1 conflict
0xc2f84a16…86b8
0x34b655…2a6f
4 touches
1 conflict
0xc57b566d…8591
0x34b655…2a6f
4 touches
1 conflict
0xda46a376…f6a6
0x34b655…2a6f
4 touches
1 conflict
0xe6917e4a…8571
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity