← previous blocknext block →recent activity
Analyzing
Block #87,504,445
16 transactions · 14 stateful · 2026-07-13 14:40:40 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,504,445 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w08w111w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0aa42ae9…ed69
0x34b655…2a6f
4 touches
1 conflict
0x3439dfbc…0d03
0x34b655…2a6f
4 touches
1 conflict
0x41d9a134…ccfe
0x34b655…2a6f
4 touches
1 conflict
0x4ce41dcc…e297
0x34b655…2a6f
4 touches
1 conflict
0x67db761a…4fa1
0x34b655…2a6f
4 touches
1 conflict
0x7b6d2deb…dde0
0x34b655…2a6f
4 touches
1 conflict
0x83e779c0…b0c2
0x34b655…2a6f
4 touches
1 conflict
0x84ecc7b6…d90e
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 0x0aa42ae9bd…54ed69
Audit this contract →
← previous block·next block →recent activity