← previous blocknext block →recent activity
Analyzing
Block #75,943,777
12 transactions · 11 stateful · 2026-05-21 01:15:27 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,943,777 · 12 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
4w05w06w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x00bac013…a28c
0x91b81b…6d56
4 touches
1 conflict
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0x177b4669…4051
0x065c9d…c394
2 touches
0 conflicts
0x2b4ad252…8098
0x065c9d…c394
2 touches
0 conflicts
0x2d48283a…6b33
0x065c9d…c394
2 touches
0 conflicts
0x6c0be066…91ce
0x065c9d…c394
2 touches
0 conflicts
0xbc183e57…03cf
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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity