← previous blocknext block →recent activity
Analyzing
Block #77,783,208
16 transactions · 12 stateful · 2026-05-29 13:30:42 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #77,783,208 · 16 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
1w02w13w24w05w16w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x7bc84cbd…f493
0x851145…3f07
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x8d0d8061…d410
0xc8689a…ee79
6 touches
3 conflicts
0x0fde64da…aa3e
0x2a68ba…90c5
6 touches
3 conflicts
0xcfe06a18…b5b5
0x69df8a…6292
6 touches
3 conflicts
0x259ee49c…49df
0x69df8a…6292
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: 0xab35264b…1cfa38
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity