← previous blocknext block →recent activity
Analyzing
Block #87,410,406
22 transactions · 21 stateful · 2026-07-13 04:11:49 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,410,406 · 22 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
1w06w17w08w19w210w011w113w014w115w216w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e49f754…23a2
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x1c03f81f…b304
0x34b655…2a6f
4 touches
1 conflict
0x30480a53…166b
0x34b655…2a6f
4 touches
1 conflict
0x453f53a8…e541
0x34b655…2a6f
4 touches
1 conflict
0x4b0a67ef…b8ba
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
10 conflicts on slot 0x9e49f754f7…be23a2
Audit this contract →
← previous block·next block →recent activity