← previous blocknext block →recent activity
Analyzing
Block #75,019,971
8 transactions · 6 stateful · 2026-05-16 18:22:06 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,019,971 · 8 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
1w03w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fbde2b3…9b8f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x037849a8…fa88
0x34b655…2a6f
2 touches
0 conflicts
0x44f26cbe…58c2
0x34b655…2a6f
2 touches
0 conflicts
0x71e4ffd1…9beb
0x34b655…2a6f
2 touches
0 conflicts
0x7dd1c9ce…5c0e
0x34b655…2a6f
2 touches
0 conflicts
0x967123a1…901f
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: Perpl
1 conflict on slot 0x8fbde2b3d3…899b8f
Audit this contract →
← previous block·next block →recent activity