← previous blocknext block →recent activity
Analyzing
Block #87,612,726
22 transactions · 16 stateful · 2026-07-14 02:45:35 UTC
Parallelism
86/100
Blocked
25%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,612,726 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w09w115w016w217w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x4a0328ea…d46c
0x34b655…2a6f
4 touches
1 conflict
0x270d9018…5084
0x065c9d…c394
3 touches
1 conflict
0x013426c3…eb56
0x065c9d…c394
3 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity