← previous blocknext block →recent activity
Analyzing
Block #75,099,898
17 transactions · 16 stateful · 2026-05-17 03:15:03 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,099,898 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w09w010w111w012w113w114w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xb9868b52…c77f
0x34b655…2a6f
8 touches
6 conflicts
0x41d3bfa5…523e
0x34b655…2a6f
6 touches
3 conflicts
0x56c6a014…3aaa
0x34b655…2a6f
6 touches
3 conflicts
0x8404070b…464d
0x34b655…2a6f
4 touches
1 conflict
0x58fd0045…0803
0x96b79e…d00a
4 touches
1 conflict
0x00000000…003d
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
6 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity