← previous blocknext block →recent activity
Analyzing
Block #87,487,693
17 transactions · 16 stateful · 2026-07-13 12:48:31 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,487,693 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w28w311w012w113w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x521f03f8…dc0e
0x34b655…2a6f
8 touches
6 conflicts
0xe2c66a2e…150f
0x34b655…2a6f
8 touches
6 conflicts
0x015c28a0…37da
0x34b655…2a6f
4 touches
1 conflict
0x0c0eefa8…3e5f
0x34b655…2a6f
4 touches
1 conflict
0x1175233a…64e7
0x34b655…2a6f
4 touches
1 conflict
0x6aca3a74…ce9a
0x34b655…2a6f
4 touches
1 conflict
0x6be6c2df…d9c0
0x34b655…2a6f
4 touches
1 conflict
0x744b7ced…47a4
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 0x521f03f844…eedc0e
Audit this contract →
← previous block·next block →recent activity