← previous blocknext block →recent activity
Analyzing
Block #75,262,413
8 transactions · 7 stateful · 2026-05-17 21:20:24 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,262,413 · 8 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0a809ce1…7894
0x34b655…2a6f
4 touches
1 conflict
0x6caf33e2…c261
0x34b655…2a6f
4 touches
1 conflict
0x16cb3442…057c
0x065c9d…c394
2 touches
0 conflicts
0x6c4fa074…adcd
0x065c9d…c394
2 touches
0 conflicts
0x6d29427a…fc82
0x065c9d…c394
2 touches
0 conflicts
0xb4bd958b…7f76
0x065c9d…c394
2 touches
0 conflicts
0xbce67a96…ad00
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity