← previous blocknext block →recent activity
Analyzing
Block #76,346,897
12 transactions · 9 stateful · 2026-05-22 22:00:17 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,346,897 · 12 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
1w05w06w17w28w311w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
8 touches
6 conflicts
0x5149ba0e…d954
0x754704…b603
6 touches
3 conflicts
0xd58b5c38…3b7c
0x754704…b603
6 touches
3 conflicts
0x532023a5…d800
0xe52b14…7230
6 touches
3 conflicts
0x8ffa3328…ce11
0xe52b14…7230
6 touches
3 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x441ebe8e…c411
0x34b655…2a6f
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: 0xe52b1424…bb7230
6 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity