← previous blocknext block →recent activity
Analyzing
Block #75,678,715
12 transactions · 11 stateful · 2026-05-19 19:49:30 UTC
Parallelism
50/100
Blocked
45%
Avg conflicts / tx
1.08
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,678,715 · 12 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w29w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c913164…5c2e
0x34b655…2a6f
10 touches
10 conflicts
0xf853eb8e…4027
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x3c83275e…d7c2
0x34b655…2a6f
6 touches
3 conflicts
0xc6417de0…2191
0xc8689a…ee79
4 touches
1 conflict
0x0711ec2d…d973
0x34b655…2a6f
4 touches
1 conflict
0x1179284b…db76
0x34b655…2a6f
4 touches
1 conflict
0x7170c140…36bc
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: Perpl
10 conflicts on slot 0x1c913164f5…845c2e
Audit this contract →
← previous block·next block →recent activity