← previous blocknext block →recent activity
Analyzing
Block #87,596,078
16 transactions · 11 stateful · 2026-07-14 00:54:16 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,596,078 · 16 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
4w05w16w07w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e13b7b0…e55c
0x34b655…2a6f
4 touches
1 conflict
0xc514314c…1aa4
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x30c5329c…711c
0x34b655…2a6f
4 touches
1 conflict
0x8e628d8b…3d19
0x34b655…2a6f
4 touches
1 conflict
0x470dfce9…75c3
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x4e13b7b079…0ae55c
Audit this contract →
← previous block·next block →recent activity