← previous blocknext block →recent activity
Analyzing
Block #75,846,690
21 transactions · 18 stateful · 2026-05-20 14:28:31 UTC
Parallelism
81/100
Blocked
44%
Avg conflicts / tx
0.81
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,846,690 · 21 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
2w03w14w06w07w18w011w112w214w318w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x451e482b…7e7d
0x34b655…2a6f
8 touches
6 conflicts
0x353fc724…f222
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
6 touches
3 conflicts
0x99a21305…dffc
0x2a68ba…90c5
6 touches
3 conflicts
0x1fff6dcb…b3f4
0xc8689a…ee79
6 touches
3 conflicts
0xa605468c…1bfc
0x1d1325…2305
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: Perpl
6 conflicts on slot 0x451e482b59…427e7d
Audit this contract →
← previous block·next block →recent activity