← previous blocknext block →recent activity
Analyzing
Block #87,709,817
14 transactions · 12 stateful · 2026-07-14 13:34:48 UTC
Parallelism
57/100
Blocked
50%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,709,817 · 14 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
2w03w14w27w39w410w511w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
4 touches
1 conflict
0xb678410a…0edb
0x34b655…2a6f
4 touches
1 conflict
0xbf768a2f…f453
0x34b655…2a6f
4 touches
1 conflict
0xc26efdc7…f8be
0x34b655…2a6f
4 touches
1 conflict
0xc835a767…1ac6
0x34b655…2a6f
4 touches
1 conflict
0xdfbd8991…5bd1
0x34b655…2a6f
4 touches
1 conflict
0xfef0ce0a…aa80
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity