← previous blocknext block →recent activity
Analyzing
Block #87,576,327
15 transactions · 14 stateful · 2026-07-13 22:42:09 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,576,327 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w17w18w010w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xda12e7f3…e890
0x34b655…2a6f
6 touches
3 conflicts
0x1172247d…0022
0x34b655…2a6f
4 touches
1 conflict
0x1f6de02e…874b
0x34b655…2a6f
4 touches
1 conflict
0x27762dc0…0664
0x34b655…2a6f
4 touches
1 conflict
0x5b6a7552…a4b8
0x34b655…2a6f
4 touches
1 conflict
0x68d9d4e4…91b6
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity