← previous blocknext block →recent activity
Analyzing
Block #75,255,243
17 transactions · 13 stateful · 2026-05-17 20:32:14 UTC
Parallelism
71/100
Blocked
54%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,255,243 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w28w09w110w311w415w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49bc8810…08ef
0x065c9d…c394
8 touches
6 conflicts
0xf3d7a307…4d63
0x065c9d…c394
8 touches
6 conflicts
0x9fc6ea79…e2dc
0x34b655…2a6f
8 touches
6 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
6 touches
3 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0xdc308125…5135
0x34b655…2a6f
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: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0x49bc8810d5…5c08ef
Audit this contract →
← previous block·next block →recent activity