← previous blocknext block →recent activity
Analyzing
Block #77,349,171
17 transactions · 17 stateful · 2026-05-27 13:17:32 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,349,171 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w07w18w19w010w111w113w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x75d17fe1…81a4
0xa6afd3…d132
4 touches
1 conflict
0xb24a9fb5…f3d7
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0000
0xa9fb85…c84d
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
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: 0x681e908b…e1ae09
1 conflict on slot 0x0d622e34f9…000000
Audit this contract →
← previous block·next block →recent activity