← previous blocknext block →recent activity
Analyzing
Block #87,622,822
15 transactions · 13 stateful · 2026-07-14 03:53:04 UTC
Parallelism
73/100
Blocked
23%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,622,822 · 15 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
2w03w17w08w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ee4a6d2…6389
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xdb7c435f…f490
0x34b655…2a6f
6 touches
3 conflicts
0x0dcb313d…7073
0x34b655…2a6f
4 touches
1 conflict
0x1487893e…4055
0x34b655…2a6f
4 touches
1 conflict
0x176771f9…c1a4
0x34b655…2a6f
4 touches
1 conflict
0x17c70f19…23a7
0x34b655…2a6f
4 touches
1 conflict
0x19e9a11b…e981
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
3 conflicts on slot 0x1ee4a6d212…536389
Audit this contract →
← previous block·next block →recent activity