← previous blocknext block →recent activity
Analyzing
Block #87,456,636
17 transactions · 16 stateful · 2026-07-13 09:20:54 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,456,636 · 17 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
1w02w14w05w28w39w010w111w213w014w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc55fba3…d23e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x53f7214d…8ec6
0x34b655…2a6f
4 touches
1 conflict
0x694bf0dd…d36b
0x34b655…2a6f
4 touches
1 conflict
0x6a07f9d4…c440
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x737fb258…1ad3
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 0xcc55fba3f9…65d23e
Audit this contract →
← previous block·next block →recent activity