← previous blocknext block →recent activity
Analyzing
Block #77,220,723
11 transactions · 9 stateful · 2026-05-26 23:00:30 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,220,723 · 11 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
1w02w13w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2fc05e8…5252
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0x91b81b…6d56
4 touches
1 conflict
0x9560013d…8caf
0x91b81b…6d56
4 touches
1 conflict
0x455b104f…3960
0xea1b8e…c5ec
4 touches
1 conflict
0xa5bbce14…e473
0xea1b8e…c5ec
4 touches
1 conflict
0xa5bbce14…e474
0xea1b8e…c5ec
4 touches
1 conflict
0xb6b74ae0…8d5e
0xea1b8e…c5ec
4 touches
1 conflict
0xf9112568…5c23
0x065c9d…c394
3 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: LeverUp: LeverUp
1 conflict on slot 0xc2fc05e867…605252
Audit this contract →
← previous block·next block →recent activity