← previous blocknext block →recent activity
Analyzing
Block #87,724,400
19 transactions · 19 stateful · 2026-07-14 15:12:31 UTC
Parallelism
68/100
Blocked
37%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,724,400 · 19 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
4w05w18w09w110w211w312w413w514w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0x09a15b10…2639
0x754704…b603
12 touches
15 conflicts
0x5149ba0e…d954
0x754704…b603
12 touches
15 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
12 touches
15 conflicts
0x3845e7dc…c691
0xe52b14…7230
12 touches
15 conflicts
0x532023a5…d800
0xe52b14…7230
12 touches
15 conflicts
0x6cc5ca07…1020
0xe52b14…7230
12 touches
15 conflicts
0x75162976…43c3
0xe52b14…7230
12 touches
15 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: 0xe52b1424…bb7230
15 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity