← previous blocknext block →recent activity
Analyzing
Block #87,623,463
26 transactions · 23 stateful · 2026-07-14 03:57:22 UTC
Parallelism
69/100
Blocked
57%
Avg conflicts / tx
1.31
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,623,463 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w18w29w310w413w114w215w416w523w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd026fe03…7748
0x34b655…2a6f
12 touches
15 conflicts
0x0804b2ba…8a77
0x34b655…2a6f
8 touches
6 conflicts
0x1ee4a6d2…6389
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
6 touches
3 conflicts
0x1175233a…64e7
0x34b655…2a6f
6 touches
3 conflicts
0x18e900fa…07f4
0x34b655…2a6f
6 touches
3 conflicts
0x42341814…60f1
0x34b655…2a6f
6 touches
3 conflicts
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
15 conflicts on slot 0xd026fe0331…887748
Audit this contract →
← previous block·next block →recent activity