← previous blocknext block →recent activity
Analyzing
Block #87,710,352
36 transactions · 34 stateful · 2026-07-14 13:38:23 UTC
Parallelism
61/100
Blocked
71%
Avg conflicts / tx
2.69
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,710,352 · 36 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w28w09w110w211w312w413w514w615w716w817w918w1021w122w223w824w328w429w534w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x0dd44476…ef40
0x34b655…2a6f
8 touches
6 conflicts
0x2d7ea048…d78e
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0xc26efdc7…f8be
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xdfbd8991…5bd1
0x34b655…2a6f
8 touches
6 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
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity