← previous blocknext block →recent activity
Analyzing
Block #76,527,207
11 transactions · 8 stateful · 2026-05-23 18:01:03 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,527,207 · 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
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xadd5ff7c…8925
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0497b7e5…4b3c
0x065c9d…c394
2 touches
0 conflicts
0x1a58128b…0ee6
0x065c9d…c394
2 touches
0 conflicts
0x23289878…3d4f
0x065c9d…c394
2 touches
0 conflicts
0x5fc11ca7…cbf4
0x065c9d…c394
2 touches
0 conflicts
0x6ffad3f7…f7db
0x065c9d…c394
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: Perpl
1 conflict on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity