← previous blocknext block →recent activity
Analyzing
Block #87,704,056
30 transactions · 25 stateful · 2026-07-14 12:56:14 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,704,056 · 30 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
2w04w05w16w28w110w011w114w215w317w018w119w223w124w225w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18ec97d9…6baa
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0001
0xc1ff9f…b0fc
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x6fca8941…b68b
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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
6 conflicts on slot 0x18ec97d97d…d36baa
Audit this contract →
← previous block·next block →recent activity