← previous blocknext block →recent activity
Analyzing
Block #87,723,651
16 transactions · 16 stateful · 2026-07-14 15:07:30 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,723,651 · 16 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
2w03w16w210w311w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x287d8ffe…95ad
0x34b655…2a6f
4 touches
1 conflict
0x5eb5d9be…b2c1
0x34b655…2a6f
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xa3a621f8…75a2
0x34b655…2a6f
4 touches
1 conflict
0xb65644e3…33ce
0x34b655…2a6f
4 touches
1 conflict
0xbfb7adca…51d7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
1 conflict on slot 0x287d8ffeef…ab95ad
Audit this contract →
← previous block·next block →recent activity