← previous blocknext block →recent activity
Analyzing
Block #75,610,051
7 transactions · 5 stateful · 2026-05-19 12:10:46 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,610,051 · 7 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb06e76e0…51cb
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b77
0x34b655…2a6f
2 touches
0 conflicts
0x6d1b72ee…6b78
0x34b655…2a6f
2 touches
0 conflicts
0x9a291a56…9a9c
0x34b655…2a6f
2 touches
0 conflicts
0x4299e60d…44f2
0x57ea24…2cec
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 0xb06e76e0d7…0651cb
Audit this contract →
← previous block·next block →recent activity