← previous blocknext block →recent activity
Analyzing
Block #75,838,050
15 transactions · 10 stateful · 2026-05-20 13:30:25 UTC
Parallelism
87/100
Blocked
30%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,838,050 · 15 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
1w04w16w08w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a809ce1…7894
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x50910633…5225
0x2a68ba…90c5
4 touches
1 conflict
0x309ef367…e8a1
0x34b655…2a6f
4 touches
1 conflict
0x310a7246…2dcb
0x34b655…2a6f
2 touches
0 conflicts
0x4118bd12…924a
0x34b655…2a6f
2 touches
0 conflicts
0x43aded3f…9805
0x34b655…2a6f
2 touches
0 conflicts
0x44ab25fb…e044
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 0x0a809ce130…5f7894
Audit this contract →
← previous block·next block →recent activity