← previous blocknext block →recent activity
Analyzing
Block #87,503,784
29 transactions · 24 stateful · 2026-07-13 14:36:12 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,503,784 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w06w19w011w113w016w118w219w321w126w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
8 touches
6 conflicts
0x7b2f3e6d…978f
0x34b655…2a6f
6 touches
3 conflicts
0x0adf48a7…c84a
0x34b655…2a6f
4 touches
1 conflict
0x13a332bb…0a80
0x34b655…2a6f
4 touches
1 conflict
0x15554b7b…e30e
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
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 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity