← previous blocknext block →recent activity
Analyzing
Block #87,715,691
19 transactions · 16 stateful · 2026-07-14 14:14:10 UTC
Parallelism
89/100
Blocked
19%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,715,691 · 19 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
1w02w03w18w012w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb6eb5df…6c71
0x34b655…2a6f
4 touches
1 conflict
0xc36c840c…e955
0x40c49f…2af0
4 touches
1 conflict
0x76d1e78d…7877
0x40c49f…2af0
4 touches
1 conflict
0x2ad33f95…4aee
0x40c49f…2af0
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x4f575ddf…12bd
0x34b655…2a6f
4 touches
1 conflict
0x588380ee…0a5c
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 0xfb6eb5df19…d96c71
Audit this contract →
← previous block·next block →recent activity