← previous blocknext block →recent activity
Analyzing
Block #87,348,098
14 transactions · 13 stateful · 2026-07-12 21:15:01 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,348,098 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w07w18w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6f10f11…2018
0x34b655…2a6f
4 touches
1 conflict
0xedcfbee7…ea97
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x8a35acfb…d1a9
0xb1dbf0…c0d3
4 touches
1 conflict
0xb07a0849…3b62
0xb1dbf0…c0d3
4 touches
1 conflict
0xe684760e…ece0
0x34b655…2a6f
4 touches
1 conflict
0x6bbdd0f7…1d2a
0x34b655…2a6f
4 touches
1 conflict
0xa209b7b4…206c
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
1 conflict on slot 0xd6f10f1187…a72018
Audit this contract →
← previous block·next block →recent activity