← previous blocknext block →recent activity
Analyzing
Block #87,626,977
25 transactions · 19 stateful · 2026-07-14 04:20:53 UTC
Parallelism
76/100
Blocked
42%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,626,977 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w18w011w012w113w014w115w216w319w420w522w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x925c118c…a1d8
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xc02164e2…de47
0x065c9d…c394
4 touches
1 conflict
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0x13510de3…1c68
0x34b655…2a6f
4 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0x49f75237…44f4
0x34b655…2a6f
4 touches
1 conflict
0x4aa7bc6e…96f3
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
6 conflicts on slot 0x925c118c7b…bea1d8
Audit this contract →
← previous block·next block →recent activity