← previous blocknext block →recent activity
Analyzing
Block #87,313,620
17 transactions · 16 stateful · 2026-07-12 17:24:27 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,313,620 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w07w09w111w113w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb835d684…089c
0x34b655…2a6f
4 touches
1 conflict
0xbe581d31…e0b9
0x34b655…2a6f
4 touches
1 conflict
0xc550cc48…815d
0x34b655…2a6f
4 touches
1 conflict
0xc550cc48…815e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0c9eb6ea…7c39
0x34b655…2a6f
4 touches
1 conflict
0x1e22ba11…b783
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 0xb835d6849b…41089c
Audit this contract →
← previous block·next block →recent activity