← previous blocknext block →recent activity
Analyzing
Block #87,579,673
10 transactions · 7 stateful · 2026-07-13 23:04:32 UTC
Parallelism
60/100
Blocked
43%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,579,673 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ae834f7…a036
0x34b655…2a6f
6 touches
3 conflicts
0x3f93d576…f1de
0x34b655…2a6f
6 touches
3 conflicts
0xfffe583a…9130
0x34b655…2a6f
4 touches
1 conflict
0xd42fdceb…d86a
0x34b655…2a6f
4 touches
1 conflict
0xdb7c435f…f490
0x34b655…2a6f
4 touches
1 conflict
0xea0fee48…1fab
0x34b655…2a6f
4 touches
1 conflict
0x410b84ab…1dbc
0x34b655…2a6f
4 touches
1 conflict
0x4cfbc6b1…2649
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 0x2ae834f7e9…b9a036
Audit this contract →
← previous block·next block →recent activity