← previous blocknext block →recent activity
Analyzing
Block #87,497,937
29 transactions · 24 stateful · 2026-07-13 13:57:05 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,497,937 · 29 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
1w02w04w15w27w08w09w110w211w315w120w121w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0xc1ff9f…b0fc
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xd2b87a88…aa57
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xa37d59c6…996b
0x34b655…2a6f
4 touches
1 conflict
0xb670a63e…ead8
0x34b655…2a6f
4 touches
1 conflict
0xbe0b0914…7e36
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: 0xc1ff9fef…f4b0fc
6 conflicts on slot 0x0000000000…000001
Audit this contract →
← previous block·next block →recent activity