← previous blocknext block →recent activity
Analyzing
Block #87,726,369
19 transactions · 17 stateful · 2026-07-14 15:25:41 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,726,369 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w112w213w016w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0001
0xc1ff9f…b0fc
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x94ba9c4a…41d8
0x34b655…2a6f
4 touches
1 conflict
0xb4fbfa0e…694e
0x34b655…2a6f
4 touches
1 conflict
0xc9dce17a…a1a1
0x34b655…2a6f
4 touches
1 conflict
0xca3d94bc…7502
0x34b655…2a6f
4 touches
1 conflict
0xf31b6b3f…055e
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity