← previous blocknext block →recent activity
Analyzing
Block #87,871,842
20 transactions · 18 stateful · 2026-07-15 07:38:45 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,871,842 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w410w011w112w218w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
6 touches
3 conflicts
0x8561290a…9f07
0x0a2fbf…29b1
6 touches
3 conflicts
0x8561290a…9f08
0x0a2fbf…29b1
6 touches
3 conflicts
0x8561290a…9f0b
0x0a2fbf…29b1
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5c677e67…7636
0x34b655…2a6f
6 touches
3 conflicts
0x55b4e430…44cb
0x754704…b603
6 touches
3 conflicts
0xb3e53c5e…b99c
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: 0x0a2fbf2d…f729b1
3 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity