← previous blocknext block →recent activity
Analyzing
Block #75,269,014
16 transactions · 13 stateful · 2026-05-17 22:04:38 UTC
Parallelism
81/100
Blocked
46%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,269,014 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w19w010w112w113w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0004
0xd5b70d…615b
4 touches
1 conflict
0x35b65947…44d1
0xc8689a…ee79
4 touches
1 conflict
0x00000000…0000
0xd5b70d…615b
4 touches
1 conflict
0x00000000…0002
0xd5b70d…615b
4 touches
1 conflict
0x18aed20c…48f3
0x000000…012a
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
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
3 conflicts on slot 0x801a6e5726…c1d85c
Audit this contract →
← previous block·next block →recent activity