← previous blocknext block →recent activity
Analyzing
Block #87,716,190
21 transactions · 19 stateful · 2026-07-14 14:17:33 UTC
Parallelism
81/100
Blocked
32%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,716,190 · 21 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
1w03w07w18w011w213w115w318w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd36917c…b88b
0x34b655…2a6f
6 touches
3 conflicts
0x0ea46b1d…c9a4
0x34b655…2a6f
4 touches
1 conflict
0x33633f8e…2a99
0x34b655…2a6f
4 touches
1 conflict
0x40883ce5…2ae2
0x34b655…2a6f
4 touches
1 conflict
0x42dd9d36…3fc0
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5cd36012…d899
0x34b655…2a6f
4 touches
1 conflict
0x70e3da66…674a
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 0xdd36917cc2…d4b88b
Audit this contract →
← previous block·next block →recent activity