← previous blocknext block →recent activity
Analyzing
Block #77,341,048
14 transactions · 9 stateful · 2026-05-27 12:23:29 UTC
Parallelism
86/100
Blocked
22%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,341,048 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc56294b3…4af5
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0fde64da…aa3e
0x2a68ba…90c5
2 touches
0 conflicts
0x76e96198…eec4
0x2a68ba…90c5
2 touches
0 conflicts
0x08d53462…97ef
0x69df8a…6292
2 touches
0 conflicts
0x10abefc9…c9bc
0x69df8a…6292
2 touches
0 conflicts
0x10d80fee…dbda
0x69df8a…6292
2 touches
0 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: 0xa6afd386…b0d132
1 conflict on slot 0xc56294b31f…664af5
Audit this contract →
← previous block·next block →recent activity